Opened 14 years ago
Closed 10 years ago
#6482 closed bug (no change required)
gdb should not stop program on SIGCONT
| Reported by: | pulkomandy | Owned by: | nobody |
|---|---|---|---|
| Priority: | normal | Milestone: | Unscheduled |
| Component: | Applications/Command Line Tools | Version: | R1/Development |
| Keywords: | Cc: | ||
| Blocked By: | Blocking: | ||
| Platform: | All |
Description
According to http://www.delorie.com/gnu/docs/gdb/gdb_39.html : "Normally, GDB is set up to let the non-erroneous signals like SIGALRM be silently passed to your program"
On Haiku, SIGCONT is sent as part of the normal function of the program. However, gdb intercept it, which makes it annoying to debug GUI apps in Haiku. One workaround is :
handle SIGCONT nostop
at gdb prompt. But this is quite annoying to do and should be made the default behaviour.
Change History (3)
comment:1 by , 14 years ago
comment:2 by , 10 years ago
| Milestone: | R1 → Unscheduled |
|---|
Now that we have a nice Debugger, this doesn't really need to be in R1 anymore.
comment:3 by , 10 years ago
| Resolution: | → no change required |
|---|---|
| Status: | new → closed |
GDB was outsourced and updated to a (somewhat) newer version; if this issue persists please report it at HaikuPorts.
Note:
See TracTickets
for help on using tickets.
While I agree with you, you can help yourself in the mean time by adding a /boot/home/.gdbinit file with the above contents.
You could also define macros there; there are some nice scripts on the net which help with inspecting STL containers, etc.