From: Tom Tromey <tromey@redhat.com>
To: Joel Brobecker <brobecker@adacore.com>
Cc: Jim Blandy <jimb@red-bean.com>,
Pedro Alves <pedro@codesourcery.com>,
gdb-patches@sourceware.org
Subject: Re: RFA: Building GDB under GLIBC 2.8
Date: Mon, 29 Dec 2008 23:48:00 -0000 [thread overview]
Message-ID: <m3ljtyzgte.fsf@fleche.redhat.com> (raw)
In-Reply-To: <20081229055001.GK4216@adacore.com> (Joel Brobecker's message of "Mon\, 29 Dec 2008 09\:50\:01 +0400")
>>>>> "Joel" == Joel Brobecker <brobecker@adacore.com> writes:
Joel> Looks OK to me. I'm a little bit pained by seeing us forced to check
Joel> return values in cases where we really don't care, but if this is
Joel> the way things are going to be in glibc from now on. Were the glibc
Joel> developers contacted and do we know what they said? I'm wondering
Joel> if these new attributes are a done-deal or whether there are
Joel> re-considering...
You must ask for this checking. It is only enabled if you use
-D_FORTIFY_SOURCE=2. glibc is working as intended here, as this
checking is part of the point of this feature.
The problem is that some distros enable this by default. And, other
distros build their packages this way as a security measure. So, it
is handy if gdb is modified to conform. The alternative is the
distros carrying their own patches for this, plus developers on Ubuntu
having to do something special.
Tom
next prev parent reply other threads:[~2008-12-29 23:48 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-13 2:05 Jim Blandy
2008-12-13 20:33 ` Mark Kettenis
2008-12-13 23:02 ` Andreas Schwab
2008-12-14 6:08 ` Jim Blandy
2008-12-14 19:57 ` Mark Kettenis
2008-12-14 21:54 ` Paul Pluzhnikov
2008-12-14 18:26 ` Jan Kratochvil
2008-12-14 18:26 ` RFA: Building GDB under GLIBC 2.8 [resend w/the patch] Jan Kratochvil
2008-12-15 9:02 ` RFA: Building GDB under GLIBC 2.8 Jim Blandy
2008-12-15 20:07 ` Tom Tromey
2008-12-15 20:17 ` Pedro Alves
2008-12-20 0:46 ` Jim Blandy
2008-12-29 5:50 ` Joel Brobecker
2008-12-29 23:48 ` Tom Tromey [this message]
2009-01-06 18:32 ` Jim Blandy
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=m3ljtyzgte.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=jimb@red-bean.com \
--cc=pedro@codesourcery.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