Closed Bug 1039053 Opened 10 years ago Closed 8 years ago

Create debug eng pvt_builds for the Flame with symbols

Categories

(Release Engineering :: General, defect)

ARM
Gonk (Firefox OS)
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED WONTFIX

People

(Reporter: gkw, Unassigned)

References

()

Details

The engineering builds that we prebuild for the Flame are opt-only. It will be extremely useful to have debug prebuilt binaries created as well (to run tests or otherwise). We can then detect assertions. Jesse also mentioned that policy violations can also be detected in debug builds.
Summary: Create debug eng pvt_builds for the Flame → Create debug eng pvt_builds for the Flame with symbols
https://pvtbuilds.mozilla.org/pvt/mozilla.org/b2gotoro/nightly/mozilla-central-flame-eng/latest/ b2g-34.0a1.en-US.android-arm.crashreporter-symbols.zip are the symbols for the build and b2g-34.0a1.en-US.android-arm.tar.gz is the gecko gaia.zip is the gaia portion. You can flash the device using the TWQA flash tool and download the symbols separately. Would that work?
Flags: needinfo?(gary)
Getting symbols would just mean that we will have readable crash stacks in an opt build, but that might not change whether assertions are shown or not.
Flags: needinfo?(gary) → needinfo?(nhirata.bugzilla)
Oh that is true. Which flags do we need in order to get the asserts? DEBUG=1?
Flags: needinfo?(nhirata.bugzilla)
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → WONTFIX
Component: General Automation → General
You need to log in before you can comment on or make changes to this bug.