From: Gary Benson <gbenson@redhat.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: dje@google.com, jan.kratochvil@redhat.com,
gdb-patches@sourceware.org, mark@klomp.org
Subject: Re: [RFA take 6] Allow setting breakpoints on inline functions (PR 10738)
Date: Thu, 15 Mar 2012 18:10:00 -0000 [thread overview]
Message-ID: <20120315181002.GA10803@redhat.com> (raw)
In-Reply-To: <833999wxkt.fsf@gnu.org>
Eli Zaretskii wrote:
> > Date: Thu, 15 Mar 2012 10:51:17 +0000
> > From: Gary Benson <gbenson@redhat.com>
> > Cc: Jan Kratochvil <jan.kratochvil@redhat.com>, gdb-patches@sourceware.org,
> > Eli Zaretskii <eliz@gnu.org>, Mark Wielaard <mark@klomp.org>
> >
> > Jan, Doug, Eli, how do you feel about "possibly inconsistent"?
> >
> > The option text would become:
> >
> > "Do not reject possibly inconsistent .gdb_index sections."
>
> The meaning of that is that the sections being skipped are
> inconsistent within themselves. If that's really what you meant,
> I'm fine with the change.
The issue is that with older index section the information in the
.gdb_index sections is not consistent with the information that GDB
would generate from the DWARF. Does that make sense?
Thanks,
Gary
--
http://gbenson.net/
next prev parent reply other threads:[~2012-03-15 18:10 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-14 13:38 Gary Benson
2012-03-14 17:51 ` Doug Evans
2012-03-14 17:55 ` Jan Kratochvil
2012-03-14 17:58 ` Doug Evans
2012-03-15 10:51 ` Gary Benson
2012-03-15 10:52 ` Jan Kratochvil
2012-03-15 16:51 ` Doug Evans
2012-03-15 18:04 ` Eli Zaretskii
2012-03-15 18:10 ` Gary Benson [this message]
2012-03-15 18:15 ` Eli Zaretskii
2012-03-15 18:26 ` Gary Benson
2012-03-15 18:31 ` Pedro Alves
2012-03-15 18:36 ` Eli Zaretskii
2012-03-15 18:40 ` Jan Kratochvil
2012-03-15 19:29 ` Gary Benson
2012-03-15 19:34 ` Doug Evans
2012-03-15 19:52 ` Pedro Alves
2012-03-15 20:06 ` Pedro Alves
2012-03-16 10:03 ` Gary Benson
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=20120315181002.GA10803@redhat.com \
--to=gbenson@redhat.com \
--cc=dje@google.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=jan.kratochvil@redhat.com \
--cc=mark@klomp.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