From: Stuart Pook <linux-bluetooth4@pook.es>
To: Stuart Pook <linux-bluetooth4@pook.es>, linux-bluetooth@vger.kernel.org
Subject: Re: bluetoothd 4.37 -> Segmentation fault
Date: Wed, 29 Apr 2009 18:14:55 +0200 [thread overview]
Message-ID: <49F87CFF.4090804@pook.es> (raw)
In-Reply-To: <20090429160430.GA25611@jh-x301>
hi Johan
Johan Hedberg wrote:
> It'd be good if you could get a trace with debug symbols so we see the
> exact line numbers.
Why don't I have debug symbols? Does the default make not add debug symbols? I guess that I'll have to look at how I call configure.
> However, before that could you check with latest git
> if you still experience this crash.
Do I have to update the client plugins as well or can I mix a bluetoothd from git with the plugins from 4.37?
> There's at least one commit since
> 4.37 (7fb4d906c00bf6e2ed03cc3e880bab52b8a984d6) that fixes a crash issue
> with client_free.
Should I always try the git version before reporting bugs?
Stuart
next prev parent reply other threads:[~2009-04-29 16:14 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 [this message]
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
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=49F87CFF.4090804@pook.es \
--to=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