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

List:       kde-bugs-dist
Subject:    [kdevplatform] [Bug 331910] Debugger component crashing for null pointer in Variables
From:       Niko Sams <niko.sams () gmail ! com>
Date:       2014-03-10 6:15:14
Message-ID: bug-331910-17878-9BwESsVCEe () http ! bugs ! kde ! org/
[Download RAW message or body]

https://bugs.kde.org/show_bug.cgi?id=331910

Niko Sams <niko.sams@gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |RESOLVED
         Resolution|---                         |WONTFIX

--- Comment #3 from Niko Sams <niko.sams@gmail.com> ---
That would work for your code but not for any other case where the variable is
deleted implicitly. (goes out of scope, deleted in a called method etc).

Additionally we would have to parse and understand the source code in gdb
plugin - which we don't do at all currently.

Question is how do other gdb frontends (QtCreator, Eclipse) handle this
situation? Maybe you could test that and report here?

-- 
You are receiving this mail because:
You are watching all bug changes.
[prev in list] [next in list] [prev in thread] [next in thread]