Closed
Bug 389442
Opened 18 years ago
Closed 18 years ago
Staging server minidump_stackwalk returning unexpected results
Categories
(mozilla.org Graveyard :: Server Operations, task)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: benjamin, Assigned: reed)
Details
Attachments
(1 file)
|
52.21 KB,
text/plain
|
Details |
The minidump_stackwalk program on staging is returning unexpected results which causes odd exceptions during processing:
runProcessor for f29da7b3-3a19-11dc-80d9-001321b0783d
Caught Error: exceptions.ValueError
need more than 5 values to unpack
File "/opt/breakpad_source/processor/socorro/lib/monitor.py", line 117, in runProcessor
processor.process(dir, dumpID, report)
File "/opt/breakpad_source/processor/socorro/lib/processor.py", line 58, in process
report = self.processDump(dumpPath, jsonPath, dumpID, report)
File "/opt/breakpad_source/processor/socorro/lib/processor.py", line 71, in processDump
threads = report.read_stackframes(fh)
File "/opt/breakpad_source/processor/socorro/models/__init__.py", line 546, in read_stackframes
(thread_num, frame_num, module_name, function, source, source_line, instruction) = map(EmptyFilter, line.split("|"))
To diagnose, can you please run the following command and attach the output to this bug?:
First find f29da7b3-3a19-11dc-80d9-001321b0783d.dmp, which should be in the directory configured to save failed dumps. If we're not saving failed minidumps, I can attach one to the bug.
/path/to/minidump_stackwalk -m /path/to/f29da7b3-3a19-11dc-80d9-001321b0783d.dmp /mnt/socorro/symbols/symbols_ffx /mnt/socorro/symbols/symbols_os
| Assignee | ||
Comment 1•18 years ago
|
||
This is output for the .dmp that benjamin sent me
| Assignee | ||
Updated•18 years ago
|
Assignee: aravind → reed
| Assignee | ||
Comment 2•18 years ago
|
||
I recompiled the minidump_stackwalk binary, as per luser's recommendation, and it doesn't sigsegv now.
Status: NEW → RESOLVED
Closed: 18 years ago
Resolution: --- → FIXED
Updated•11 years ago
|
Product: mozilla.org → mozilla.org Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•