Johan Hedberg wrote:
> Hi,
> 
> On Sat, Feb 21, 2009, Jelle de Jong wrote:
>> When running the bluetoothd daemon it segfaults when a devices tries
>> to connect, please see the debug attachments, what is going wrong
>> here? and how can I provide more useful debug info. I compiled with
>> debug flags please see the attachment for how I compiled and made the
>> Debian packages for testing.
> 
> The recent BtIO rework has changed quite alot of bluez code during this
> week so the code base is inevitably less stable than it used to be. We
> will try to iron out any outstanding issues during the next few days.
> 
> Could you describe in more detail the steps you've taken to make
> bluetoothd segfault? I have not been able to reproduce this with my own
> tests (mainly testing HFP, A2DP and Serial functionalities).
> 
> Your backtraces also didn't seem to contain much useful info. What I
> usually do is after a git clone/pull I compile with
> ./bootstrap-configure && make
> and then I can use the src/.libs/bluetoothd binary for debuging (e.g.
> with valgrind or gdb). The --enable-maintainer-mode switch that
> bootstrap-configure uses makes the produced bluetoothd binary load the
> modules from the source tree instead of their usual location
> (/usr/lib/bluetooth) which helps make sure you're only running code from
> the latest git.
> 
> Johan

Thanks Johan, for the information and your help on the irc channel,

I sent a few hours more on debugging and even while we thought we
found the issue:
http://git.kernel.org/?p=bluetooth/bluez.git;a=commit;h=8fb3fd137f3d108e373df9501915ee9ff6e23f83

The problem is still there and bluetoothd segfauls when i try to let
my bluetooth keyboard or mouse connect.

Cheers,

Jelle