From: Stefan Seyfried <stefan.seyfried@googlemail.com>
To: unlisted-recipients:; (no To-header on input)
Cc: linux-bluetooth@vger.kernel.org
Subject: Bluez 4.68 instant segfault
Date: Tue, 13 Jul 2010 10:10:07 +0200 [thread overview]
Message-ID: <20100713101007.6da560a1@susi.home.s3e.de> (raw)
Hi,
I'd say that this commit would justify an instant 4.69 release:
commit 86b16d8a63d8d6191533418dd1c38ce35c3fbf0a
Author: Marcel Holtmann <marcel@holtmann.org>
Date: Mon Jul 12 23:59:34 2010 -0300
Remove double g_option_context_free() call
Without that, "bluetoothd --udev" instant segfaults, while without --udev
it gets aborted by glibc due tot the double free ;)
Thanks,
Stefan
--
Stefan Seyfried
"Any ideas, John?"
"Well, surrounding them's out."
next reply other threads:[~2010-07-13 8:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-13 8:10 Stefan Seyfried [this message]
2010-07-13 11:49 ` Bluez 4.68 instant segfault 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=20100713101007.6da560a1@susi.home.s3e.de \
--to=stefan.seyfried@googlemail.com \
--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;
as well as URLs for NNTP newsgroup(s).