Closed
Bug 847268
Opened 12 years ago
Closed 12 years ago
Provide partners on what information to get when device freezes
Categories
(Firefox OS Graveyard :: General, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: jcheng, Assigned: alan.yenlin.huang)
Details
Attachments
(5 files)
(deleted),
patch
|
Details | Diff | Splinter Review | |
(deleted),
patch
|
Details | Diff | Splinter Review | |
(deleted),
patch
|
Details | Diff | Splinter Review | |
(deleted),
patch
|
Details | Diff | Splinter Review | |
(deleted),
application/octet-stream
|
Details |
No description provided.
Reporter | ||
Comment 1•12 years ago
|
||
Alan, can you help to provide it? thanks
Assignee: nobody → ahuang
Summary: Provide partners on what information to get when device freeze → Provide partners on what information to get when device freezes
Assignee | ||
Comment 2•12 years ago
|
||
Assignee | ||
Comment 3•12 years ago
|
||
Assignee | ||
Comment 4•12 years ago
|
||
Assignee | ||
Comment 5•12 years ago
|
||
Assignee | ||
Comment 6•12 years ago
|
||
Assignee | ||
Comment 7•12 years ago
|
||
[Note] Use no optimization build to make sure symbols could be parsed correctly:
Add "export B2G_NOOPT=1" in .userconfig under b2g root folder.
If these are cases that b2g process still alive (using "adb shell b2g-ps" could still see process /system/b2g/b2g), then use gdb to get backtrace information:
./run-gdb.sh attach
(gdb) thread apply all bt
(and maybe more gdb debug commands...)
If these are cases that b2g process no longer exist (B2G process crash), then partners would need a build with coredump enabled or minidump enabled:
1. Use coredump (recommanded)
1-a. Enable coredump in boot.img. attachment 721597 [details] [diff] [review] is an example to enable it in init.rc (ramdisk)
1-b. Build gecko with attachment 721600 [details] [diff] [review] patch.
1-c. Apply attachment 721579 [details] [diff] [review] patch for run-gdb.sh to parse coredump
Then, if B2G process crashed, you could pull coredump from device and uses below command to debug:
./run-gdb.sh --coredump [PROGRAM] [COREDUMP FILE]
(Then use gdb debug commands...)
2. Use minidump
2-a. Apply attachment 721578 [details] [diff] [review] patch.
2-b. Make symbols: ". setup.sh && make buildsymbols"
2-c. Extract attachment 721602 [details] and put it under b2g root
Then, if B2G process crashed, you could pull minidump *.dmp file under /data/b2g/mozilla/Crash\ Reports/pending, and uses below command to parse debug information:
./minidump_stackwalk [dmpfile] objdir-gecko/dist/crashreporter-symbols/ > dmp_result.txt
Reporter | ||
Comment 8•12 years ago
|
||
Thanks Alan
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Assignee | ||
Comment 9•11 years ago
|
||
These patches are used to collect detailed information for partner engineering ROM debugging only. Please don't include them in user build/shipping ROM.
Comment 10•11 years ago
|
||
Can minidump and coredump both be enabled on b2g system?
Assignee | ||
Comment 11•11 years ago
|
||
(In reply to ying.xu from comment #10)
> Can minidump and coredump both be enabled on b2g system?
No, you cannot have both enabled.
Comment 12•11 years ago
|
||
(In reply to Alan Huang [:ahuang] from comment #11)
> (In reply to ying.xu from comment #10)
> > Can minidump and coredump both be enabled on b2g system?
>
> No, you cannot have both enabled.
Ying, we'll build two version for monkey test.
You need to log in
before you can comment on or make changes to this bug.
Description
•