Closed
Bug 791181
Opened 13 years ago
Closed 13 years ago
symbol files information like: source file and line of crash are not visible in Socorro GUI
Categories
(Socorro :: Backend, task)
Tracking
(Not tracked)
RESOLVED
INVALID
People
(Reporter: k_r, Unassigned)
Details
User Agent: Opera/9.80 (Windows NT 6.1; WOW64; U; en) Presto/2.10.289 Version/12.00
Steps to reproduce:
Hello,
I have converted .pdb to .sym correctly, checked sym path in processorconfig. All seems to be configure properly. Env Linux Debian6(Ubuntu) + Socorro build 981
Actual results:
So it works in command line.
/data/socorro/stackwalk/bin/minidump_stackwalk -m /var/tmp/crashdump_2.dump "/root/stackwalk_test/sym/"
2|0|xxx.exe|crash_2(int)|c:\xxx\xxx.cpp|46|0x4
We see exact code in source code.
But this will never appear under <source> tab in GUI after submitting it manually through submitter.py
python scripts/submitter.py -u http://crash-reports/submit -j /var/tmp/crash.json -d /var/tmp/crashdump_2.dump
CrashID=bp-ca635582-0545-438c-a5fa-27c472120914
Processor returns dump without any useful information regarding symbol file in <Raw Dump> section
2|0|xxx.exe||||0x1cce
Only file name and exeption.
we enabled some logging in externalprocessor.py seems that execution command and symbol file store path correct.
/data/socorro/stackwalk/bin/minidump_stackwalk -m DUMPFILEPATHNAME SYMBOL_PATHS 2>/dev/null
/data/socorro/stackwalk/bin/minidump_stackwalk -m /home/socorro/temp/781d8915-ca0e-48d6-acc6-e0e232120913.dump "/root/stackwalk_test/sym/" 2>/dev/null
analyzeFrames
2|0|xxx.exe|||| 0x1cce
Information already lost here.
If required. will attach test files aswell
Expected results:
Able to see source file name and line of crash under <source tab>
seems configuration issue
Status: UNCONFIRMED → RESOLVED
Closed: 13 years ago
Resolution: --- → INVALID
You need to log in
before you can comment on or make changes to this bug.
Description
•