From: Pedro Alves <palves@redhat.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Gary Benson <gbenson@redhat.com>,
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:31:00 -0000 [thread overview]
Message-ID: <4F623553.5050204@redhat.com> (raw)
In-Reply-To: <831uotwx2d.fsf@gnu.org>
On 03/15/2012 06:14 PM, Eli Zaretskii wrote:
>> Date: Thu, 15 Mar 2012 18:10:02 +0000
>> From: Gary Benson <gbenson@redhat.com>
>> Cc: dje@google.com, jan.kratochvil@redhat.com, gdb-patches@sourceware.org,
>> mark@klomp.org
>>
>>>> "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.
>
> Why does this happen? Is the information in those sections
> inaccurate?
A more high level alternative explanation to Gary's would be
something like:
Older GDB versions didn't use all the info from DWARF that the new
versions do, and so not all the info needed by newer GDBs is in
the older index sections (we only put there what we need). Using the
index is mutually exclusive with fetching the info out of DWARF.
So if GDB loads an older index, there are bits of info that are
missing. And, with those missing, a newer GDB will present a
worse debugging experience in terms of features and correctness
than if it didn't use the index at all, but fetched all it needed
from the DWARF.
Hope I got that right.
--
Pedro Alves
next prev parent reply other threads:[~2012-03-15 18:31 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
2012-03-15 18:15 ` Eli Zaretskii
2012-03-15 18:26 ` Gary Benson
2012-03-15 18:31 ` Pedro Alves [this message]
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=4F623553.5050204@redhat.com \
--to=palves@redhat.com \
--cc=dje@google.com \
--cc=eliz@gnu.org \
--cc=gbenson@redhat.com \
--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