From: Andreas Schwab <schwab@suse.de>
To: gdb-patches@sources.redhat.com
Subject: Re: Don't error out when variable not available
Date: Sun, 02 Jan 2005 23:49:00 -0000 [thread overview]
Message-ID: <jed5wnxuhb.fsf@sykes.suse.de> (raw)
In-Reply-To: <20050102225745.GA28488@nevyn.them.org> (Daniel Jacobowitz's message of "Sun, 2 Jan 2005 17:57:45 -0500")
Daniel Jacobowitz <drow@false.org> writes:
> How about reusing the LOC_OPTIMIZED_OUT handling to describe this case?
> I believe that will print "foo = <optimized out>".
LOC_OPTIMIZED_OUT is not a value, but a static property of a symbol. I
don't think it fits into the dynamic nature of unavailable values.
Andreas.
--
Andreas Schwab, SuSE Labs, schwab@suse.de
SuSE Linux Products GmbH, Maxfeldstraße 5, 90409 Nürnberg, Germany
Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
next prev parent reply other threads:[~2005-01-02 23:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-02 22:13 Andreas Schwab
2005-01-02 22:57 ` Daniel Jacobowitz
2005-01-02 23:49 ` Andreas Schwab [this message]
2005-01-03 0:49 ` Daniel Jacobowitz
2005-01-03 13:41 ` Andreas Schwab
2005-01-04 22:20 ` Andrew Cagney
2005-01-05 19:23 ` Andreas Schwab
2005-02-28 20:53 ` Daniel Jacobowitz
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=jed5wnxuhb.fsf@sykes.suse.de \
--to=schwab@suse.de \
--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