From: Joel Brobecker <brobecker@adacore.com>
To: Jan Kratochvil <jan.kratochvil@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: quick status on gdb-7.2.1 & gdb-7.3? (Mar 07)
Date: Wed, 09 Mar 2011 05:29:00 -0000 [thread overview]
Message-ID: <20110309042615.GT30306@adacore.com> (raw)
In-Reply-To: <20110308182421.GA9555@host1.jankratochvil.net>
> FYI worth considering is a gcc-4.6 bug workaround for GDB:
> http://sourceware.org/bugzilla/show_bug.cgi?id=12435
>
> But it should be fixed for gcc-4.6.0 GA so maybe GDB does not have to care.
Normally, I would say that we should be resilient to debug info
bugs. In this particular case, the decision is a little harder
to take, because it appears that the bug does not appear in a
GCC release (and hopefully won't); and also, the fix is in a
sensitive area... That being said, I don't have a particular
objection to the fix if it doesn't complexify the code too much,
and some comments are added.
--
Joel
prev parent reply other threads:[~2011-03-09 4:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-07 12:43 Joel Brobecker
2011-03-07 14:47 ` Joel Brobecker
2011-03-07 22:26 ` Tom Tromey
2011-03-08 8:26 ` Joel Brobecker
2011-03-08 10:02 ` Jan Kratochvil
2011-03-08 18:38 ` Jan Kratochvil
2011-03-09 5:29 ` Joel Brobecker [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=20110309042615.GT30306@adacore.com \
--to=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=jan.kratochvil@redhat.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