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

List:       kdevelop-bugs
Subject:    [Bug 148581] New: kdevelop's debugger incorrectly handles breakpoints
From:       Alexandre Nunes <alexandre.nunes () gmail ! com>
Date:       2007-08-06 16:58:30
Message-ID: 20070806185829.148581.alexandre.nunes () gmail ! com
[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=148581         
           Summary: kdevelop's debugger incorrectly handles breakpoints
           Product: kdevelop
           Version: 3.4.1
          Platform: unspecified
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: NOR
         Component: general
        AssignedTo: kdevelop-bugs kdevelop org
        ReportedBy: alexandre.nunes gmail com


Version:           3.4.1 (using KDE 3.5.7, Debian Package 4:3.5.7.dfsg.1-3 \
                (lenny/sid))
Compiler:          Target: i486-linux-gnu
OS:                Linux (i686) release 2.6.22.1

kdevelop does a "set stop-on-solib-events" on gdb inconditionally, as a way of \
handling pending breakpoints on old gdb versions.

With recent gdb versions, that's not necessary. But kdevelop does that anyway, and \
when the user does e.g. a next on a function which generates a solib event, gdb \
issues an event and kdevelop tells gdb to continue running. The next is thus not \
respected, and the program behaves like the user would have issued a continue \
request. The user gets confused, waiting for the control to return from the function, \
but the control is way ahead.

manually forcing gdb to disable stop-on-solib-events solves that issue.

_______________________________________________
KDevelop-bugs mailing list
KDevelop-bugs@kdevelop.org
https://barney.cs.uni-potsdam.de/mailman/listinfo/kdevelop-bugs


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