linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: Stefan Seyfried <stefan.seyfried@googlemail.com>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: Bluez 4.68 instant segfault
Date: Tue, 13 Jul 2010 08:49:06 -0300	[thread overview]
Message-ID: <1279021746.6282.13.camel@localhost.localdomain> (raw)
In-Reply-To: <20100713101007.6da560a1@susi.home.s3e.de>

Hi Stefan,

> 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 ;)

yes it justify a new release. I am getting to it today.

Regards

Marcel



      reply	other threads:[~2010-07-13 11:49 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-13  8:10 Bluez 4.68 instant segfault Stefan Seyfried
2010-07-13 11:49 ` Marcel Holtmann [this message]

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=1279021746.6282.13.camel@localhost.localdomain \
    --to=marcel@holtmann.org \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=stefan.seyfried@googlemail.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;
as well as URLs for NNTP newsgroup(s).