Opened 16 years ago
Closed 16 years ago
#3492 closed bug (duplicate)
[gdb] Quiting Terminal Does Not Close Gdb
| Reported by: | Adek336 | Owned by: | axeld |
|---|---|---|---|
| Priority: | normal | Milestone: | R1 |
| Component: | Applications | Version: | R1/pre-alpha1 |
| Keywords: | Cc: | ||
| Blocked By: | Blocking: | ||
| Platform: | All |
Description
Use Deskbar to debug some thread. Now perform a command which results in long output, "threads apply all bt" should do the trick. You need an output sufficiently long to get a
--- Type <return> to continue, or q <return> to quit---
Leave gdb in this state and use Terminal->Quit in the debug window.
Experienced behaviour: the terminal closes, but the debugged team is now frozen and the gdb team is still running. Expected : terminal closes, gdb terminates, debugged team continues to run.
Change History (4)
comment:1 by , 16 years ago
comment:3 by , 16 years ago
| Blocked By: | 3340 added |
|---|---|
| Resolution: | → duplicate |
| Status: | new → closed |
Indeed a dup of #3340.
comment:4 by , 16 years ago
| Blocked By: | 3340 removed |
|---|
(In #3340) Likely a kernel or TTY problem. I believe I've also seen programs started in the terminal continue running after the Terminal was closed, which is probably the same issue. Assigning to myself for the time being.
Note:
See TracTickets
for help on using tickets.
Killing the gdb team unfreezes the debugged team.