From: Jim Blandy <jimb@redhat.com>
To: Andrew Cagney <ac131313@redhat.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [6.0] PROBLEMS and NEWS
Date: Tue, 23 Sep 2003 22:00:00 -0000 [thread overview]
Message-ID: <vt2he33cgn9.fsf@zenia.home> (raw)
In-Reply-To: <3F70A3C2.5080504@redhat.com>
Andrew Cagney <ac131313@redhat.com> writes:
> >> +DWARF 2 Location Expressions allow the compiler to more exactly
> >> +describe the location of variables to the debugger.
> > It'd be nice to give some indication of why the user would care about
> > this, like: "Taken together with Dwarf 2 Call Frame Information,
> > location expressions give GDB the information it needs to debug
> > optimized code much more effectively."
>
> At one stage I had the word optimized, but took it out. I've changed it to:
>
> DWARF 2 Location Expressions allow the compiler to more completly
> describe the location of variables (even in optimized code) to the
> debugger.
You're right --- it's always better to describe things that way. How
hard the compiler worked to generate the code isn't the point: how
accurately the compiler describes whatever it produces is.
I'd say "more accurately" instead of "more completely", since the most
common manifestation of the old problem was that GDB was wrong about
the location of the variable, not that it couldn't find the variable.
next prev parent reply other threads:[~2003-09-23 22:00 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-20 20:59 Andrew Cagney
2003-09-20 22:35 ` Daniel Jacobowitz
2003-09-20 23:39 ` Andrew Cagney
2003-09-22 7:21 ` Andrew Cagney
2003-09-22 19:12 ` Andrew Cagney
2003-09-22 22:16 ` Jim Blandy
2003-09-23 19:49 ` Andrew Cagney
2003-09-23 22:00 ` Jim Blandy [this message]
2003-09-25 18:30 ` Andrew Cagney
2003-09-22 7:38 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=vt2he33cgn9.fsf@zenia.home \
--to=jimb@redhat.com \
--cc=ac131313@redhat.com \
--cc=gdb-patches@sources.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