Confirmed users
2,317
edits
MozillaQualityAssurance:Home Page:Firefox 3.0 TestPlan:Debug-Builds: Difference between revisions
MozillaQualityAssurance:Home Page:Firefox 3.0 TestPlan:Debug-Builds (view source)
Revision as of 19:30, 11 October 2007
, 11 October 2007no edit summary
No edit summary |
No edit summary |
||
| Line 22: | Line 22: | ||
* QA will run a FFT during the Firefox 3 Beta Period with this Debug Builds for Memory Leaks | * QA will run a FFT during the Firefox 3 Beta Period with this Debug Builds for Memory Leaks | ||
* QA file Bugs for this Memory Leaks and Assertions | * QA file Bugs for this Memory Leaks and Assertions | ||
* Additional Information from a mail from dbaron: | |||
The reason they're so large (-g) is independent of the reason most | |||
people want them (-DDEBUG, plus a few other things like | |||
--enable-trace-malloc). You could do one without the other. (In | |||
fact, it's possible that the packaging code will automatically strip | |||
out the debug symbols.) | |||
That said, having the debugging symbols is necessary if you're using | |||
nsTraceRefcnt or trace-malloc for more than summary statistics or | |||
leak detection. It might be necessary for distinguishing leak bugs, | |||
since the stack traces aren't so great without them. | |||
= Target = | = Target = | ||