[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kdevelop-bugs
Subject:    [Bug 135979] New: With gdb 6.5 variables watch out of scope generate
From:       Dario Vecchio <dariovecchio () tiscali ! it>
Date:       2006-10-19 17:28:46
Message-ID: 20061019192845.135979.dariovecchio () tiscali ! it
[Download RAW message or body]

------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
         
http://bugs.kde.org/show_bug.cgi?id=135979         
           Summary: With gdb 6.5 variables watch out of scope generate an
                    error message box at every debugger step
           Product: kdevelop
           Version: unspecified
          Platform: unspecified
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: NOR
         Component: general
        AssignedTo: kdevelop-bugs kdevelop org
        ReportedBy: dariovecchio tiscali it


Version:           3.4 SVN rev 597183 (using KDE KDE 3.5.1)
Compiler:          gcc 4.1.0 
OS:                Linux

Debugging (gdb 6.5) if you add a variable watch (say val) and then step out of the variable
    scope the debugger shows an error message box (must close it every time) but you cannot
    delete the watch from the "Variable" window because the invalid watch is disabled, so at every
    debugger step you get the error and must close the message box.
    I think should be better to mark (with different color or with a xxx value or whatever else better
    but not disable) the invalid watch in the "Variable" window without display any message box.
    Note that with gdb 6.4 there is not the problem but there are error messages closing the application
    under debug.
    Maybe kdevelop should test the gdb version (does it now?) to manage the different behaviours.


[prev in list] [next in list] [prev in thread] [next in thread]