From: Jim Blandy <jimb@codesourcery.com>
To: "Rob Quill" <rob.quill@gmail.com>
Cc: gdb@sourceware.org
Subject: Re: Variable values before initialisaton
Date: Tue, 28 Nov 2006 19:29:00 -0000 [thread overview]
Message-ID: <m3irgztln0.fsf@codesourcery.com> (raw)
In-Reply-To: <baf6008d0611280320g20e2c205u722e915caabc795f@mail.gmail.com> (Rob Quill's message of "Tue, 28 Nov 2006 11:20:54 +0000")
"Rob Quill" <rob.quill@gmail.com> writes:
> Interesting. Is it that GCC doesn't implement it, or that GDB doesn't
> understand it, or both? How difficult to you think it would be to
> implement, because I think it would be quite good to have it right.
Neither GCC nor GDB emit DW_AT_start_scope. I don't know about GCC,
but it would be somewhat involved in GDB; you'd have to change
read_lexical_block_scope in dwarf2read.c to produce a bunch of nested
blocks.
I'm gathering from your comments that the you've been assuming that
GCC + DWARF + GDB present an accurate model of the execution of the
source program. But the only (significant to development) consumer of
the model we actually present has been humans and the test suite, so
little issues like this haven't been tended to very carefully, since
humans don't mind them. I don't want to discourage you, but I think
you'll find more as you go along, and some may be a lot of work to
fix.
prev parent reply other threads:[~2006-11-28 19:29 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-23 17:12 Rob Quill
2006-11-23 17:27 ` Vladimir Prus
[not found] ` <baf6008d0611230932o355f2ba6h9f6b0e778c82bce@mail.gmail.com>
2006-11-23 17:32 ` Rob Quill
2006-11-23 19:55 ` Daniel Jacobowitz
2006-11-23 19:58 ` Rob Quill
2006-11-24 6:53 ` Vladimir Prus
2006-11-24 15:15 ` Daniel Jacobowitz
2006-11-27 20:09 ` Jim Blandy
2006-11-28 11:21 ` Rob Quill
2006-11-28 19:29 ` Jim Blandy [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=m3irgztln0.fsf@codesourcery.com \
--to=jimb@codesourcery.com \
--cc=gdb@sourceware.org \
--cc=rob.quill@gmail.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