From: Eli Zaretskii <eliz@gnu.org>
To: Tom Tromey <tromey@redhat.com>
Cc: jan.kratochvil@redhat.com, aburgess@broadcom.com,
gdb-patches@sourceware.org
Subject: Re: PATCH: error reading variable: value has been optimized out
Date: Fri, 31 Aug 2012 09:59:00 -0000 [thread overview]
Message-ID: <83fw73qt4m.fsf@gnu.org> (raw)
In-Reply-To: <871uisibi3.fsf@fleche.redhat.com>
> From: Tom Tromey <tromey@redhat.com>
> Cc: Andrew Burgess <aburgess@broadcom.com>, "gdb-patches\@sourceware.org" <gdb-patches@sourceware.org>
> Date: Mon, 27 Aug 2012 09:46:12 -0600
>
> Offhand it seems as though read_frame_register_value could create an
> lval_computed value if any register it needs is optimized out. I don't
> know whether this is worth the effort.
IMO, any enhancements that allow better support for optimized-out
variables are important. Having GDB refuse to show a value of a
variable, letting you go hunt for it via disassembly and register
sniffing, is among the worst user-experiences I have debugging
optimized programs.
next prev parent reply other threads:[~2012-08-31 9:59 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-24 12:11 Andrew Burgess
2012-08-26 18:22 ` Jan Kratochvil
2012-08-27 15:46 ` Tom Tromey
2012-08-31 9:59 ` Eli Zaretskii [this message]
2012-09-03 15:07 ` Jan Kratochvil
2012-08-31 10:33 ` Andrew Burgess
2012-09-01 8:17 ` Eli Zaretskii
2012-09-03 8:32 ` Andrew Burgess
2012-09-03 11:24 ` Jan Kratochvil
2012-09-03 15:38 ` Eli Zaretskii
2012-09-03 15:17 ` Jan Kratochvil
2012-09-04 16:58 ` Andrew Burgess
2012-09-05 18:54 ` Jan Kratochvil
2012-09-12 17:30 ` Tom Tromey
2012-09-13 12:34 ` Andrew Burgess
2012-09-14 19:02 ` Tom Tromey
2012-09-14 21:39 ` Andrew Burgess
2012-09-17 16:57 ` Jan Kratochvil
2012-09-19 14:29 ` Andrew Burgess
2012-09-20 13:28 ` Jan Kratochvil
2012-09-21 17:19 ` Andrew Burgess
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=83fw73qt4m.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=aburgess@broadcom.com \
--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