From: Elena Zannoni <ezannoni@redhat.com>
To: Jim Blandy <jimb@redhat.com>
Cc: Elena Zannoni <ezannoni@redhat.com>,
David Carlton <carlton@kealia.com>,
gdb-patches@sources.redhat.com
Subject: Re: [rfa] add 'parent' field to struct die_info
Date: Thu, 02 Oct 2003 16:00:00 -0000 [thread overview]
Message-ID: <16252.19978.310797.582904@localhost.redhat.com> (raw)
In-Reply-To: <vt2n0cjiqlo.fsf@zenia.home>
Jim Blandy writes:
>
> Elena Zannoni <ezannoni@redhat.com> writes:
> > Each debugging information entry is defined either to have child
> > entries or not to have child entries. If an entry is defined not to
> > have children, the next physically succeeding entry is a sibling. If
> > an entry is defined to have children, the next physically succeeding
> > entry is its first child. Additional children are represented as
> > siblings of the first child. A chain of sibling entries is terminated
> > by a null entry.
>
> Sure, that sort of explanation would be appropriate for the die
> reading code, but I think it would just be confusing for 'struct
> die_info'. Once we've built the die tree in memory, all that detail
> is gone, and you've just got the pure tree structure. There's no
> concept of "the next physically succeeding entry", for example.
whatever
prev parent reply other threads:[~2003-10-02 16:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-30 16:29 David Carlton
2003-09-30 22:13 ` Jim Blandy
2003-09-30 22:54 ` David Carlton
2003-10-01 17:24 ` Elena Zannoni
2003-10-02 4:07 ` Jim Blandy
2003-10-02 15:44 ` Elena Zannoni
2003-10-02 15:57 ` Jim Blandy
2003-10-02 16:00 ` Elena Zannoni [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=16252.19978.310797.582904@localhost.redhat.com \
--to=ezannoni@redhat.com \
--cc=carlton@kealia.com \
--cc=gdb-patches@sources.redhat.com \
--cc=jimb@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