Closed Bug 672564 Opened 9 years ago Closed 9 years ago

build and deploy custom ROM for tegras use for test automation

Categories

(Release Engineering :: General, defect)

x86_64
Linux
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED WONTFIX

People

(Reporter: blassey, Assigned: dougt)

References

Details

(Whiteboard: [android_tier_1])

The stacks we get from the tegras can be completely useless if the crash in libc (or any other system lib) since we don't have symbols for those libraries and we don't have frame pointers.

Building our own ROM would be a simple way to ensure we have symbols for all our crash stacks.
This is fairly crazy, like void-your-warranty-but-not-quite-brick-the-dev-board-crazy, but we could try building a normal 2.2 image with -fno-omit-frame-pointer and -g if we need it (and NEON off), and then drop the resulting libc.so into /system/lib.  At worst, nothing works and we have to reflash.

This wouldn't get us crash-report symbols from libc unless we breakpad-ified the custom lib, and it obviously wouldn't help with crashes in other system-libraries, but it should be relatively simple to try and would allow us to walk out of libc and into libxul on crashes.
I'm not sure what component this bug should be in, but it's not yet an Operations bug. RelEng? Tools?
Assignee: server-ops-releng → nobody
Component: Server Operations: RelEng → Release Engineering
QA Contact: zandr → release
Assignee: nobody → doug.turner
Whiteboard: [android_tier_1]
Now that we have decent crash reports coming in, should we just close this bug as wontfix?
I'm +1 for that
Comments 3 & 4 make this wontfix
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → WONTFIX
Product: mozilla.org → Release Engineering
You need to log in before you can comment on or make changes to this bug.