From: "Pierre Muller" <pierre.muller@ics-cnrs.unistra.fr>
To: <tromey@redhat.com>
Cc: "'Jan Kratochvil'" <jan.kratochvil@redhat.com>,
<gdb-patches@sourceware.org>
Subject: RE: [RFA] PR 11530: Fix and test case
Date: Wed, 05 May 2010 21:44:00 -0000 [thread overview]
Message-ID: <003001caec9c$2ef93de0$8cebb9a0$@muller@ics-cnrs.unistra.fr> (raw)
In-Reply-To: <m3iq78zw5d.fsf@fleche.redhat.com>
> -----Message d'origine-----
> De : gdb-patches-owner@sourceware.org [mailto:gdb-patches-
> owner@sourceware.org] De la part de Tom Tromey
> Envoyé : Friday, April 30, 2010 7:30 PM
> À : Pierre Muller
> Cc : 'Jan Kratochvil'; gdb-patches@sourceware.org
> Objet : Re: [RFA] PR 11530: Fix and test case
>
> >>>>> "Pierre" == Pierre Muller <pierre.muller@ics-cnrs.unistra.fr>
> writes:
>
> Pierre> I just want to fix the simple case in which there is
> Pierre> no, name conflict.
>
> It seems pretty reasonable to me.
>
> Pierre> With my patch, GDB will find the first instance
> Pierre> that matches the field name, but I don't even know
> Pierre> if the ordering given by the debug information necessarily
> Pierre> follows the definition order in the source!
>
> I skimmed this part of the DWARF 4 spec (5.5.6 Data Member Entries) but
> I didn't see any such requirement.
>
> I'm not too concerned about this.
>
> Pierre> Anyhow, this patch is only useful for sizeof (),
> Pierre> not for printing of the value itself, which
> Pierre> was already working...
>
> That is interesting. Why does it work in one case but not the other?
for the first test 'p a.i'
gdb calls search_struct_field,
which has already some code (around line 1842)
to cope for unnamed fields.
There was no equivalent in the lookup_struct_elt_type
function.
By the way, the search_struct_field function
also allows a union called "else" to be searched.
Should this also be inserted into lookup_struct_elt_type
or is this only a left over from Chill language?
Pierre
next prev parent reply other threads:[~2010-05-05 21:44 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-29 21:50 Pierre Muller
2010-04-30 8:20 ` Jan Kratochvil
2010-04-30 11:08 ` Joseph S. Myers
2010-04-30 13:12 ` Pierre Muller
[not found] ` <15700.946111656$1272633144@news.gmane.org>
2010-04-30 17:29 ` Tom Tromey
2010-05-05 21:44 ` Pierre Muller [this message]
[not found] ` <28104.8831450336$1273095904@news.gmane.org>
2010-05-07 17:45 ` Tom Tromey
[not found] <36245.8778698512$1272577829@news.gmane.org>
2010-04-30 17:26 ` Tom Tromey
2010-05-05 22:11 ` Pierre Muller
[not found] ` <1723.54181199825$1273097500@news.gmane.org>
2010-05-07 17:45 ` Tom Tromey
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='003001caec9c$2ef93de0$8cebb9a0$@muller@ics-cnrs.unistra.fr' \
--to=pierre.muller@ics-cnrs.unistra.fr \
--cc=gdb-patches@sourceware.org \
--cc=jan.kratochvil@redhat.com \
--cc=tromey@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