#12317: Debugger (silent?) crash, incomplete report
-------------------------------------+----------------------------
Reporter: ttcoder | Owner: anevilyak
Type: bug | Status: new
Priority: normal | Milestone: Unscheduled
Component: Applications/Debugger | Version: R1/Development
Resolution: | Keywords:
Blocked By: | Blocking:
Has a Patch: 0 | Platform: All
-------------------------------------+----------------------------
Comment (by ttcoder):
@anevilyak Wondering -- what happens if another, still ongoing, thread of
the 'crashed' team brutally calls `kill_thread()' on the segfault'ed
thread?
Thinking specifically of ticket:12319, whose [https://dev.haiku-
os.org/attachment/ticket/12319/class_NetworktimeprefletAsAddon.cpp#L55
kill_thread] occurs in the 'main' thread, separate from the one that
crashes, and ''occurs after a 2 seconds delay, presumably even if the team
has tripped into Debugger'' ?.
When I have time I'll make a quick experiment, make the thread crash
reliably by adding a `char * ptr = NULL; puts(a);` statement in the above
mentionned thread code, wait 2 seconds before clicking "debugger" or "save
report", to see if that's enough to reproduce the problems: I'll check..
- if the thread has indeed disappeared from the list
- if there's hints of a Debugger segfault in syslog (though that issue
seems to deserve a separate ticket)
--
Ticket URL: <https://dev.haiku-os.org/ticket/12317#comment:4>
Haiku <https://dev.haiku-os.org>
Haiku - the operating system.
