When a bluetooth client asks the obex-data-server for a file it crashes. Reproducible: Always Steps to Reproduce: 1. Start obex-data-server 2. Start a bluetooth client 3. Try to transfair a file from the server to the client Actual Results: SIGSEGV Expected Results: Send the file Tried it with two PCs, one with x86- and one with amd64-architekture. When I open the transfaired file on the client the content is: "<?x" (which isn't the original content) dmesg says: obex-data-serve[7567]: segfault at 0 ip 080591f4 sp bfa14f30 error 4 in obex-data-server[8048000+22000] On the x86 PC i tried to debug (and decidet to use the newest ebuilds for that), so I made: ACCEPT_KEYWORDS="~x86" USE="debug" CFLAGS="-g" emerge -av --oneshot glibc openobex obex-data-server After that I startet the server like this: taxi@schlepptop ~ $ gdb /usr/bin/obex-data-server warning: Can not parse XML syscalls information; XML support was disabled at compile time. GNU gdb (Gentoo 7.0.1 p1) 7.0.1 Copyright (C) 2009 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "i686-pc-linux-gnu". For bug reporting instructions, please see: <http://bugs.gentoo.org/>... Reading symbols from /usr/bin/obex-data-server...(no debugging symbols found)...done. (gdb) set args -n (gdb) run Starting program: /usr/bin/obex-data-server -n [Thread debugging using libthread_db enabled] obex-data-server 0.4.5 [...] when it should transfair the file (called test.txt) it outputs: obex_data_indication(): Got 10 bytes msg len=13 CMD_SETPATH requested current path: /home/taxi/bluetooth-exchange root path: /home/taxi/bluetooth-exchange new path: /home/taxi/bluetooth-exchange Tx: A0 00 03 obex_data_request(): len = 3 bytes do_write(): sending 3 bytes io callback obex_data_indication(): Got 26 bytes msg len=29 CMD_GET requested stream_fd=-1 Program received signal SIGSEGV, Segmentation fault. 0xb7de00ab in ?? () from /lib/libc.so.6 (gdb) So I think it tries to send the file (in an xml layer?) and crashes after it sendet "<?x", which is in the transfaired file. P.S. sorry for my bad english. :)
I confirm this bug. I am using obex-data-server-0.4.5.
Is this a regression over 0.4.4? Are you still able to reproduce?
My Gentoo system also suffered segfaults when transferring files over bluetooth. The patch in the link solved the segfault problem. http://bugs.muiline.com/view.php?id=493
Please retry with 0.4.6
