public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Fabien Chevalier <fabchevalier@free.fr>
To: Johan Hedberg <johan.hedberg@nokia.com>,
	Luiz Augusto von Dentz <luiz.dentz@gmail.com>
Cc: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: [Bluez-devel] Crash bug in bluez-4.4
Date: Mon, 08 Sep 2008 21:44:18 +0200	[thread overview]
Message-ID: <48C58092.7060103@free.fr> (raw)

[-- Attachment #1: Type: text/plain, Size: 1166 bytes --]

Hi All,

Just found a funny bug, steps to reproduce below:

1) make sure you have no headset whatsoever configured in bluez (fresh
empty setup)

2) Configure your asoundrc with empty bluetooth parameters

pcm.bluetooth {
         type bluetooth
}

ctl.bluetooth {
         type bluetooth
}

3)Launch your favourite ALSA base player, configure "bluetooth" as
output device

4) Hit play.

5) *BANG*
bluetoothd[17227]: Parsing
/usr/local/stow/bluez-4.4/etc/bluetooth/audio.conf failed: No such file
or directory
bluetoothd[17227]: Unix socket created: 13
bluetoothd[17227]: Telephony plugin initialized
bluetoothd[17227]: HFP AG features: (none)
bluetoothd[17227]: Accepted new client connection on unix socket (fd=10)
bluetoothd[17227]: Audio API: received BT_GETCAPABILITIES_REQ
Erreur de segmentation
palomino:/usr/local/stow#


Path attached fixes the bug... by removing three lines of code that seem 
to me not only a premature, but also bogus optimization :-(, that 
prevent us to trying to return the first element of an empty gslist.

However i'm not that familiar with that manager stuff and might be 
wrong, so please double check that ;-)

Cheers,

Fabien



[-- Attachment #2: audio-plugin-crashbug-fix.diff --]
[-- Type: text/plain, Size: 316 bytes --]

--- manager.c.orig	2008-09-08 21:22:06.000000000 +0200
+++ manager.c	2008-09-08 21:22:11.000000000 +0200
@@ -999,9 +999,6 @@
 {
 	GSList *l;
 
-	if (!bacmp(bda, BDADDR_ANY) && !interface && !connected)
-		return devices->data;
-
 	for (l = devices; l != NULL; l = l->next) {
 		struct audio_device *dev = l->data;
 

[-- Attachment #3: Type: text/plain, Size: 363 bytes --]

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/

[-- Attachment #4: Type: text/plain, Size: 164 bytes --]

_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

             reply	other threads:[~2008-09-08 19:44 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-08 19:44 Fabien Chevalier [this message]
2008-09-08 19:59 ` [Bluez-devel] Crash bug in bluez-4.4 Johan Hedberg

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=48C58092.7060103@free.fr \
    --to=fabchevalier@free.fr \
    --cc=bluez-devel@lists.sourceforge.net \
    --cc=johan.hedberg@nokia.com \
    --cc=luiz.dentz@gmail.com \
    /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