From: Daniel Jacobowitz <drow@mvista.com>
To: "H. J. Lu" <hjl@lucon.org>
Cc: David Carlton <carlton@kealia.com>, GDB <gdb@sources.redhat.com>
Subject: Re: gdb can't handle a DIE with both sibling and children
Date: Thu, 31 Jul 2003 20:29:00 -0000 [thread overview]
Message-ID: <20030731202935.GA18405@nevyn.them.org> (raw)
In-Reply-To: <20030731202229.GA16545@lucon.org>
On Thu, Jul 31, 2003 at 01:22:29PM -0700, H. J. Lu wrote:
> On Thu, Jul 31, 2003 at 04:02:15PM -0400, Daniel Jacobowitz wrote:
> > >
> > > I don't know for sure how DW_TAG_entry_point works. It seems to me
> > > that DW_TAG_entry_point should inherit DW_AT_accessibility and
> > > DW_AT_high_pc from its parent.
> >
> > Certainly not high_pc. Its _bounds_ are the bounds of its parent; the
> > entry point is only specific PC that gets jumped to.
>
> The entry point is DW_AT_low_pc. From what I can see, its DW_AT_high_pc
> should be the same as its parent. See
>
> http://www-sld.slac.stanford.edu/HELP/FORTRAN/STATEMENTS/ENTRY
Think about this for a moment.
DW_AT_low_pc represents a PC - an entry point.
DW_AT_low_pc + DW_AT_high_pc represents a range - a whole subroutine.
The bounds of the entry point are the bounds of the entire function, or
none at all. Inheriting DW_AT_high_pc makes no sense. In Fortran,
they represent a low_pc->high_pc range, but there are a number of other
useful meanings for it.
Besides, what would you do if a function had DW_AT_ranges?
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2003-07-31 20:29 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-31 18:13 H. J. Lu
2003-07-31 18:19 ` David Carlton
2003-07-31 18:20 ` Daniel Jacobowitz
2003-07-31 18:27 ` H. J. Lu
2003-07-31 18:47 ` Daniel Jacobowitz
2003-07-31 19:36 ` David Carlton
2003-07-31 19:56 ` H. J. Lu
2003-07-31 20:02 ` Daniel Jacobowitz
2003-07-31 20:22 ` H. J. Lu
2003-07-31 20:29 ` Daniel Jacobowitz [this message]
2003-07-31 20:58 ` H. J. Lu
2003-07-31 21:01 ` Daniel Jacobowitz
2003-07-31 20:29 ` David Carlton
2003-07-31 20:13 ` David Carlton
2003-07-31 20:37 Michael Elizabeth Chastain
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=20030731202935.GA18405@nevyn.them.org \
--to=drow@mvista.com \
--cc=carlton@kealia.com \
--cc=gdb@sources.redhat.com \
--cc=hjl@lucon.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