Closed
Bug 559255
Opened 15 years ago
Closed 14 years ago
Link to breakpad symbols used to process minidumps
Categories
(Socorro :: General, task)
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: cjones, Unassigned)
Details
Attachments
(1 file)
532 bytes,
patch
|
Details | Diff | Splinter Review |
I worked on a bug today in which libflashplayer.so prevented the crash-stats minidump_stackwalker from showing me enough frames in a hang-dump backtrace. I have a locally-modified minidump_stackwalk that scans the stack more aggressively, and I wanted to use that on the dump. Problem was it me quite a while to find out how to get the linux symbols. It would have been great if there had been a link on the crash-stats page to the symbol server URL from which the symbols were downloaded. (Or to a crash-stats-hosted file if symbols are gathered from another source.) Seems to make sense for the link to only be available to authorized users.
This might useful for mac too, I dunno.
Comment 1•15 years ago
|
||
I really don't think we need link exposed in the UI for this case. Do you know how the symbol server is structured? It's basically:
http://symbols.mozilla.org/firefox/foo.so/debugid/foo.so.sym
So for this example report:
https://crash-stats.mozilla.com/report/index/93ae760e-3e3b-4608-9452-9a3242100412
Look in the "modules" tab, see that the debugid for libxul.so is "BBA3B2A81930FCAACCEE53E210A3B6400". And construct the URL:
http://symbols.mozilla.org/firefox/libxul.so/BBA3B2A81930FCAACCEE53E210A3B6400/libxul.so.sym
You should be able to construct a simple python script which pulls these down, given a crash-report page. You can use Ted's fetch-symbols.py as a starting point if necessary: http://people.mozilla.com/~tmielczarek/fetch-symbols.py
The JSON version might be more easily processable: http://crash-stats.mozilla.com/dumps/93ae760e-3e3b-4608-9452-9a3242100412.jsonz
Reporter | ||
Comment 2•15 years ago
|
||
I would be settle for something ever so simple like
<a href="...">Minidump.dmp</a>
<a href="http://symbols.mozilla.org/firefox/bleep-blorp-symbols.txt">Symbol index</a>
Then I could copy the link, pass it to Ted's script, and be off to the races. I understand that this might be an odd place to stick this info, and I'd welcome suggestions for better places. IMHO having this next to a minidump link would be very useful.
(I tried to update MDC yesterday with instructions for constructing the bleep-blorp part, but it ate my edit.)
Comment 3•15 years ago
|
||
This bookmarklet will create links on the crash-stats page modules tab, if that helps.
Comment 4•15 years ago
|
||
Socorro doesn't really know this information, FWIW, it treats Breakpad's minidump_stackwalk as a black box that takes a minidump + a bunch of directories containing symbols, and returns a stack trace.
Comment 5•15 years ago
|
||
Also, as bsmedberg says, all the info that fetch-symbols.py needs should be available on the crash report page.
![]() |
||
Comment 6•14 years ago
|
||
Is there anything that is to be or can be done in this bug? For me, this sounds like either something not intended to be done or something not easy to do, but it's not even clear for me what the actual request here is...
Comment 7•14 years ago
|
||
Yeah, I don't think this is worth fixing as filed.
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → WONTFIX
Assignee | ||
Updated•13 years ago
|
Component: Socorro → General
Product: Webtools → Socorro
You need to log in
before you can comment on or make changes to this bug.
Description
•