#12155: Debugger crash
-------------------------------------+----------------------------
Reporter: vidrep | Owner: anevilyak
Type: bug | Status: new
Priority: normal | Milestone: Unscheduled
Component: Applications/Debugger | Version: R1/Development
Resolution: | Keywords:
Blocked By: 10292 | Blocking:
Has a Patch: 0 | Platform: All
-------------------------------------+----------------------------
Comment (by anevilyak):
The main question of interest for me right now is if the debugger is
actually busy doing something, or if it's simply asleep/idle, so it would
be nice to know its CPU usage in ProcessController looks like. The
behavior over here is that, when running through the steps immediately at
boot, web+ crashes -> save report -> debugger's busy for 30-45 seconds ->
both of them exit. Repeating the test drops that time down to more like
5-10 seconds, most likely due to disk caching. In both cases the Web+
window goes away at the same time as the debugger though, so if that's not
the same as your experience then the question is why.
Assuming it appears idle, you could try to open another debugger instance
from Deskbar, attach to the one generating the report, interrupt all its
threads (except for the debug task thread), and save a report then, if
you're able to do so. That'd at least yield some information as to what
state it's in at this point. That having been said, I'm also going to work
on some changes to revamp how things are executed in the case of launching
the debugger solely for the purpose of creating a report, which might
resolve the issue in a different way, but that will take some time, so in
the interim, trying to understand this issue would be helpful either way.
--
Ticket URL: <https://dev.haiku-os.org/ticket/12155#comment:20>
Haiku <https://dev.haiku-os.org>
Haiku - the operating system.
