This is the mail archive of the
gdb-prs@sourceware.org
mailing list for the GDB project.
[Bug gdb/13636] displays are disabled when variables becomeoptimized out
- From: "tromey at redhat dot com" <sourceware-bugzilla at sourceware dot org>
- To: gdb-prs at sourceware dot org
- Date: Wed, 01 Feb 2012 21:51:18 +0000
- Subject: [Bug gdb/13636] displays are disabled when variables becomeoptimized out
- Auto-submitted: auto-generated
- References: <bug-13636-4717@http.sourceware.org/bugzilla/>
http://sourceware.org/bugzilla/show_bug.cgi?id=13636
Tom Tromey <tromey at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |WAITING
CC| |tromey at redhat dot com
--- Comment #1 from Tom Tromey <tromey at redhat dot com> 2012-02-01 21:51:18 UTC ---
What version of gdb is this?
In 7.3 and earlier, throw_exception called disable_current_display.
This could cause a display to be disabled for any number of
unrelated reasons.
This was cleaned up in 7.4.
With CVS head, displays of optimized-out values seem to do the right thing.
The only call to disable_current_display (which prints the message you
mention) comes from infrun; and I think it is trickier to trigger that
by accident -- and in any case that is likely to be some other problem,
not related to optimized-out variables.
--
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.