public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "nickrob at snap dot net dot nz" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug mi/9752] MI -data-evaluate-expression prints optimized-out variable value as 0x0
Date: Tue, 14 Apr 2009 06:50:00 -0000 [thread overview]
Message-ID: <20090414065029.17480.qmail@sourceware.org> (raw)
In-Reply-To: <20090116210457.9752.rschooler@tilera.com>
------- Additional Comments From nickrob at snap dot net dot nz 2009-04-14 06:50 -------
Subject: MI -data-evaluate-expression prints optimized-out variable value as 0x0
> Ok, thanks.
> I didn't see this on gdb-patches.
> Anyway, it is ok with a test case.
This patch just replaces the call to val_print with one to common_val_print.
There's no test for the MI command -stack-list-locals when values are
optimized out and presumably existing tests will pick up any regressions for
this circumstance. So, what would the be the purpose of a test case in this
particular instance?
--
http://sourceware.org/bugzilla/show_bug.cgi?id=9752
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
next prev parent reply other threads:[~2009-04-14 6:50 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-16 21:04 [Bug mi/9752] New: " rschooler at tilera dot com
2009-01-16 22:17 ` [Bug mi/9752] " nickrob at snap dot net dot nz
2009-01-19 18:40 ` rschooler at tilera dot com
2009-01-19 20:29 ` nickrob at snap dot net dot nz
2009-04-12 16:54 ` tromey at redhat dot com
2009-04-13 2:23 ` nickrob at snap dot net dot nz
2009-04-13 21:58 ` tromey at redhat dot com
2009-04-14 6:50 ` nickrob at snap dot net dot nz [this message]
2009-04-14 16:20 ` tromey at redhat dot com
2009-04-15 6:54 ` nickrob at snap dot net dot nz
[not found] <bug-9752-4717@http.sourceware.org/bugzilla/>
2010-10-15 1:53 ` tromey at redhat dot com
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=20090414065029.17480.qmail@sourceware.org \
--to=sourceware-bugzilla@sourceware.org \
--cc=gdb-prs@sourceware.org \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).