[Bug gdb/13636] New: displays are disabled when variables become optimized out

[Bug gdb/13636] New: displays are disabled when variables become optimized out

[nmiell at comcast dot net]

http://sourceware.org/bugzilla/show_bug.cgi?id=13636

             Bug #: 13636
           Summary: displays are disabled when variables become optimized
                    out
           Product: gdb
           Version: unknown
            Status: NEW
          Severity: normal
          Priority: P2
         Component: gdb
        AssignedTo: unassigned@sourceware.org
        ReportedBy: nmiell@comcast.net
    Classification: Unclassified


gdb prints
    Disabling display $X to avoid infinite recursion.
    $X: $VAR = value has been optimized out
and then the user is forced to manually re-enable display $X.

Instead, gdb should print
    $X: $VAR = value has been optimized out
and never disable the display.

-- 
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.

[Bug gdb/13636] displays are disabled when variables become optimized out

[tromey at redhat dot com]

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.

[Bug gdb/13636] displays are disabled when variables become optimized out

[nmiell at comcast dot net]

http://sourceware.org/bugzilla/show_bug.cgi?id=13636

--- Comment #2 from Nicholas Miell <nmiell at comcast dot net> 2012-02-03 03:01:28 UTC ---
This is gdb-7.3.50.20110722-10.fc16.x86_64

-- 
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.

[Bug gdb/13636] displays are disabled when variables become optimized out

[tromey at redhat dot com]

http://sourceware.org/bugzilla/show_bug.cgi?id=13636

--- Comment #3 from Tom Tromey <tromey at redhat dot com> 2012-02-03 15:08:15 UTC ---
(In reply to comment #2)
> This is gdb-7.3.50.20110722-10.fc16.x86_64

Please try a newer version.
The change I referred to was committed in August:

2011-08-05  Pedro Alves  <pedro@codesourcery.com>

    * exceptions.c (throw_exception): Don't disable the current
    display.
    * printcmd.c (disable_current_display_cleanup): New function.
    (do_one_display): Install a cleanup to disable the current display
    if doing the display throws.

-- 
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.

[Bug gdb/13636] displays are disabled when variables become optimized out

[sergiodj at redhat dot com]

https://sourceware.org/bugzilla/show_bug.cgi?id=13636

Sergio Durigan Junior <sergiodj at redhat dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|WAITING                     |RESOLVED
                 CC|                            |sergiodj at redhat dot com
         Resolution|---                         |OBSOLETE

--- Comment #4 from Sergio Durigan Junior <sergiodj at redhat dot com> ---
Closing as OBSOLETE due to inactivity.  Feel free to reopen if still valid.

-- 
You are receiving this mail because:
You are on the CC list for the bug.