public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Luiz Augusto von Dentz <luiz.dentz@gmail.com>
To: Stuart Pook <linux-bluetooth4@pook.es>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: bluetoothd 4.37 -> Segmentation fault
Date: Wed, 29 Apr 2009 16:37:16 -0300	[thread overview]
Message-ID: <2d5a2c100904291237k5afa93fdo15ba4913f641f4d0@mail.gmail.com> (raw)
In-Reply-To: <49F89C94.2070604@pook.es>

Hi Stuart,

On Wed, Apr 29, 2009 at 3:29 PM, Stuart Pook <linux-bluetooth4@pook.es> wrote:
> ^Cbluetoothd[19530]: Removing adapter /org/bluez/19530/hci0
> bluetoothd[19530]: Removing device
> /org/bluez/19530/hci0/dev_00_1A_45_2F_49_98
> bluetoothd[19530]: Headset unregistered while device was connected!
> bluetoothd[19530]: telephony-dummy: device 0x4b925a8 disconnected
> bluetoothd[19530]: State changed
> /org/bluez/19530/hci0/dev_00_1A_45_2F_49_98:
> HEADSET_STATE_CONNECT_IN_PROGRESS -> HEADSET_STATE_DISCONNECTED
> bluetoothd[19530]: Unregistered interface org.bluez.Headset on path
> /org/bluez/19530/hci0/dev_00_1A_45_2F_49_98
> bluetoothd[19530]: unix_device_removed(0x4b925a8)
> ==19530== Invalid read of size 4
> ==19530==    at 0x4EEE6A0: headset_unlock (headset.c:2555)
> ==19530==    by 0x4EE4876: start_close (unix.c:1174)
> ==19530==    by 0x4EE5B5B: unix_device_removed (unix.c:1674)
> ==19530==    by 0x4EE9889: audio_device_unregister (device.c:630)
> ==19530==    by 0x4EE776D: audio_remove (manager.c:759)
> ==19530==    by 0x126799: device_remove (device.c:842)
> ==19530==    by 0x123AA5: adapter_remove (adapter.c:2461)
> ==19530==    by 0x11DEEA: manager_remove_adapter (manager.c:316)
> ==19530==    by 0x489EF06: g_slist_foreach (in
> /usr/lib/libglib-2.0.so.0.2000.1)
> ==19530==    by 0x11DF22: manager_cleanup (manager.c:321)
> ==19530==    by 0x129686: hcid_dbus_exit (dbus-common.c:158)
> ==19530==    by 0x11243F: main (main.c:426)
> ==19530==  Address 0x464 is not stack'd, malloc'd or (recently) free'd
> ==19530== ==19530== Process terminating with default action of signal 11

These looks like a ctrl+c case, although still a bug which should be
investigates this has nothing to do with the crash you have
experienced before.

-- 
Luiz Augusto von Dentz
Engenheiro de Computação

  reply	other threads:[~2009-04-29 19:37 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-29 14:26 bluetoothd 4.37 -> Segmentation fault Stuart Pook
2009-04-29 16:04 ` Johan Hedberg
2009-04-29 16:14   ` Stuart Pook
2009-04-29 16:32     ` Johan Hedberg
2009-04-29 17:26       ` Stuart Pook
2009-04-29 17:42         ` Johan Hedberg
2009-04-29 18:29           ` Stuart Pook
2009-04-29 19:37             ` Luiz Augusto von Dentz [this message]
2009-04-29 20:22               ` bluetoothd git + aplay -> pcm_write:1442: write error: Input/output error Stuart Pook
2009-05-02 18:46               ` bluetoothd git version -> Segmentation fault Stuart Pook
2009-05-02 20:06                 ` Johan Hedberg
     [not found]                 ` <20090502195708.GA28973@jh-x301>
2009-05-02 20:25                   ` bluetoothd git version -> aplay: pcm_write:1442: write error: Input/output error Stuart Pook

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=2d5a2c100904291237k5afa93fdo15ba4913f641f4d0@mail.gmail.com \
    --to=luiz.dentz@gmail.com \
    --cc=linux-bluetooth4@pook.es \
    --cc=linux-bluetooth@vger.kernel.org \
    /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