public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] hcid crash
Date: Tue, 29 Aug 2006 12:46:10 +0200	[thread overview]
Message-ID: <1156848370.5613.66.camel@aeonflux.holtmann.net> (raw)
In-Reply-To: <1156839814.8576.104.camel@localhost>

Hi Pierre-Yves,

> There seems to be a bug causing a crash in hcid, ver. 3.4.
> 
> 1) Using the DBus API, I open an RFCOMM connection to the OPP channel on
> a phone (tested with nokia n-gage and SE Z600)
> 
> 2) Once the connection is established, I shut the phone down, or force a
> bluetooth shtudown (only possible on the nokia, not allowed on the SE)
> 
> 3) hcid will crash (instantly with the nokia, after a few seconds with
> the SE).
> 
> Backtrace:
> 
> # gdb --quiet --args hcid -xn
> Using host libthread_db library "/lib/tls/libthread_db.so.1".
> (gdb) run
> Starting program: /usr/sbin/hcid -xn
> hcid[14874]: Bluetooth HCI daemon
> hcid[14874]: Register path:/org/bluez fallback:1
> hcid[14874]: HCI dev 0 registered
> hcid[14874]: Register path:/org/bluez/hci0 fallback:0
> hcid[14874]: HCI dev 0 already up
> hcid[14874]: Device hci0 has been added
> hcid[14874]: Starting security manager 0
> hcid[14874]: Device hci0 has been activated
> hcid[14874]: Connect in progress
> hcid[14874]: rfcomm_connect_cb: connected
> hcid[14874]: RFCOMM node /dev/rfcomm0 was disconnected
> *** glibc detected *** double free or corruption (fasttop): 0x080708d8
> ***
> 
> Program received signal SIGABRT, Aborted.
> 0xffffe410 in __kernel_vsyscall ()
> (gdb) bt
> #0  0xffffe410 in __kernel_vsyscall ()
> #1  0xb7e44101 in raise () from /lib/tls/libc.so.6
> #2  0xb7e457fd in abort () from /lib/tls/libc.so.6
> #3  0xb7e76ef7 in __fsetlocking () from /lib/tls/libc.so.6
> #4  0xb7e7cc16 in malloc_usable_size () from /lib/tls/libc.so.6
> #5  0xb7e7d5d9 in free () from /lib/tls/libc.so.6
> #6  0x08061096 in watch_remove (w=0x0) at glib-ectomy.c:116
> #7  0x0806146c in g_main_loop_run (loop=0x806a108) at glib-ectomy.c:324
> #8  0x0804c59b in main (argc=0, argv=0x0) at main.c:729
> 
> It is always reproducible here. I'll be glad to give any other output or
> info that may prove useful, just ask.

can you try the latest version from the CVS. I think that Johan fixed
this with the mainloop rewrite.

Regards

Marcel



-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

  reply	other threads:[~2006-08-29 10:46 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-29  8:23 [Bluez-devel] hcid crash Pierre-Yves Paulus
2006-08-29 10:46 ` Marcel Holtmann [this message]
2006-08-29 12:27   ` Pierre-Yves Paulus
2006-08-29 14:34     ` Marcel Holtmann
2006-08-29 13:23       ` Pierre-Yves Paulus
2006-08-29 17:44         ` Marcel Holtmann

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1156848370.5613.66.camel@aeonflux.holtmann.net \
    --to=marcel@holtmann.org \
    --cc=bluez-devel@lists.sourceforge.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox