Opened 7 years ago

Closed 7 years ago

Last modified 7 years ago

#10283 closed enhancement (fixed)

Debugger does not include all available information when using -s/--save-report

Reported by: pulkomandy Owned by: anevilyak
Priority: normal Milestone: Unscheduled
Component: Applications/Debugger Version: R1/Development
Keywords: Cc:
Blocked By: Blocking:
Platform: All


In the WebKit testsuite, I'm trying to automatically save debug reports instead of popping the debug_server dialog. I do this by catching relevant signals (SIGABRT and SIGSEGV), and from the signal handler, I run "Debugger -s --thread $myThread".

The resulting report includes informations about the team, but I don't get a stacktrace for the thread I asked for. It would be useful to know where the crash actually hapenned, as is the case when using the "save report" button from debug_server.

I'm guessing only stopped/crashed threads get their backtrace saved in the report?

Change History (3)

comment:1 by anevilyak, 7 years ago

Correct, the thread has to be in a stopped state of some form, as otherwise getting a backtrace isn't a reliable operation. --thread and/or --team are only used to locate the team to attach to, they don't implicitly stop the thread in question as well, though I suppose an additional CLI parameter could be added to indicate doing so.

comment:2 by anevilyak, 7 years ago

Resolution: fixed
Status: newclosed

As of hrev46507, if we're targetted at a specific thread (i.e. a --thread argument has been given) when being asked to save a report, we also ensure that the thread in question has first been stopped. Let me know if there are any issues.

comment:3 by anevilyak, 7 years ago

A race condition with the above has been addressed in hrev46516.

Note: See TracTickets for help on using tickets.