From: Tom Tromey <tromey@redhat.com>
To: Jan Kratochvil <jan.kratochvil@redhat.com>
Cc: Andrew Burgess <aburgess@broadcom.com>,
"gdb-patches\@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: PATCH: error reading variable: value has been optimized out
Date: Mon, 27 Aug 2012 15:46:00 -0000 [thread overview]
Message-ID: <871uisibi3.fsf@fleche.redhat.com> (raw)
In-Reply-To: <20120826171840.GA21205@host2.jankratochvil.net> (Jan Kratochvil's message of "Sun, 26 Aug 2012 19:18:40 +0200")
>>>>> "Jan" == Jan Kratochvil <jan.kratochvil@redhat.com> writes:
Andrew> Looking through, value.c is seems there might also support for
Andrew> having values partially optimised out, this would seem like a
Andrew> better solution, but I'm not sure the right way to hook this in,
Andrew> if anyone would like to offer suggestions I'm happy to create a
Andrew> new patch, alternatively, this could be improved on later...
Jan> GDB supports partially unavailable values from partially stored traces.
Jan> This is AFAIK not applicable for partially optimized out values.
I'm not sure whether I'm understanding your comment correctly, but gdb
does support partially optimized out values. However, these are only
supported for lval_computed values. See lval_funcs::check_validity and
check_any_valid.
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.
Tom
next prev parent reply other threads:[~2012-08-27 15:46 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 [this message]
2012-08-31 9:59 ` Eli Zaretskii
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=871uisibi3.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=aburgess@broadcom.com \
--cc=gdb-patches@sourceware.org \
--cc=jan.kratochvil@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