gdb gets SIGTRAP on every instruction after function call
Bug #230315 reported by
Dalle
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Mandriva |
Fix Released
|
High
|
|||
gdb (Debian) |
Fix Released
|
Unknown
|
|||
gdb (Ubuntu) |
Invalid
|
Undecided
|
Unassigned | ||
Hardy |
Invalid
|
Undecided
|
Unassigned | ||
linux (Ubuntu) |
Invalid
|
Undecided
|
Unassigned | ||
Hardy |
Fix Released
|
High
|
Tim Gardner |
Bug Description
The 8.04 kernel apparently has a bug that doesn't turn of the SIGTRAP after it has been handled. I had to downgrade to GG since this bug makes gdb unusable for those of us who uses function calls when we debug our programs.
Google found these two references to the problem:
http://
Changed in gdb: | |
status: | Unknown → New |
Changed in linux: | |
milestone: | ubuntu-8.04.1 → ubuntu-8.04.2 |
Changed in linux: | |
assignee: | nobody → timg-tpi |
status: | Confirmed → In Progress |
Changed in mandriva: | |
importance: | Unknown → High |
Changed in gdb (Debian): | |
status: | New → Fix Released |
To post a comment you must log in.
This problem appears too when debugging a program with kdevelop:
A message box "Program received signal SIGTRAP (Trace/breakpoint trap)" often pops up when debugging.
This bug makes 8.04 unusable as a C/C++ development environment