From: Johan Hedberg <johan.hedberg@gmail.com>
To: Bastien Nocera <hadess@hadess.net>
Cc: BlueZ development <linux-bluetooth@vger.kernel.org>
Subject: Re: current git segfaults, gdb backtraces included, pl;ease help
Date: Sun, 22 Feb 2009 21:59:06 +0200 [thread overview]
Message-ID: <20090222195906.GA22899@jh-x301> (raw)
In-Reply-To: <1235317521.3878.1123.camel@cookie.hadess.net>
Hi Bastien,
On Sun, Feb 22, 2009, Bastien Nocera wrote:
> Make BT_IO_OPT_INVALID be 0 in the enum, and you can use the GCC
> sentinel feature. Otherwise, it would have to wait for:
> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=28319
Thanks for the tip! However, there's still the problem that gcc seems to
want this parameter be of type char* and with gcc 4 gives the warning
"warning: missing sentinel in function call" because it is not. The
following page has some info about it:
http://www.linuxonly.nl/docs/2/0_Page_1.html
Johan
prev parent reply other threads:[~2009-02-22 19:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <499FDB3E.3040202@powercraft.nl>
2009-02-21 21:59 ` current git segfaults, gdb backtraces included, pl;ease help Johan Hedberg
2009-02-22 14:09 ` Jelle de Jong
2009-02-22 15:16 ` Johan Hedberg
2009-02-22 15:45 ` Bastien Nocera
2009-02-22 19:59 ` Johan Hedberg [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=20090222195906.GA22899@jh-x301 \
--to=johan.hedberg@gmail.com \
--cc=hadess@hadess.net \
--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