Opened 11 years ago
Last modified 10 years ago
#10297 new bug
[Debugger] DebugReportGenerator needs some additional error handling
Reported by: | anevilyak | Owned by: | anevilyak |
---|---|---|---|
Priority: | normal | Milestone: | Unscheduled |
Component: | Applications/Debugger | Version: | R1/Development |
Keywords: | Cc: | ||
Blocked By: | Blocking: | ||
Platform: | All |
Description
It's possible for the target team to go away while we're in the middle of generating a report, if one of the target team's threads is still active and issues an exit() or other termination call. In such a case, the report generator will currently have a high chance of hanging if it happens to be in the middle of waiting for some resource such as a stack trace to be retrieved. We need to watch for the corresponding events / worker failures and wake up/abort accordingly.
Note:
See TracTickets
for help on using tickets.
Moving Debugger related tickets out of R1 milestone (Prop #14).