Closed Bug 420317 Opened 17 years ago Closed 16 years ago

[thunderbird] Request a tinderbox setup with debug enabled and not stripped

Categories

(Mozilla Messaging Graveyard :: Release Engineering, defect, P3)

x86
Linux
defect

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: superbiskit, Unassigned)

Details

(Keywords: dev-doc-needed)

User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9b4pre) Gecko/2008021504 Minefield/3.0b4pre Build Identifier: Currently 2008-02-27-tbox Linux 2.6 -- Ubuntu 7.10 Isolating some bugs is pretty hopeless without debugging symbols. I'm currently chasing Bug#337903, but cannot trap the locations I need to. I am seriously constrained for disk space and cannot do my own build. In any case, as an experienced software tester I say the testing is not as valid unless I am testing a build that is known to be the same as the distributed build. I realize there are capacity constraints for the downloads, however it appears the tinderbox builds only keep one build up so the extra space shouldn't hurt. Of course, this can apply equally to other products -- your call. Reproducible: Always Steps to Reproduce: 1. 2. 3.
FWIW, Firefox has debug built for all 3 tier1 platforms as fast as tbox can spit them out but they don't appear to be published at http://ftp.mozilla.org/pub/mozilla.org/firefox/tinderbox-builds/
Component: Build Config → Build & Release
Product: Thunderbird → mozilla.org
QA Contact: build-config → build
Version: unspecified → other
Summary: Request a tinderbox setup with debug enabled and not stripped → [thunderbid] Request a tinderbox setup with debug enabled and not stripped
I believe there's another bug which mentions disk space issues as being the reason those are not published. I expect those are likely to need sorting out before this can be done...
Status: UNCONFIRMED → NEW
Ever confirmed: true
This might suck less if I fix bug 420474 (I'm pretty close).
triaged to ReleaseEngineering:Projects
Component: Build & Release → Release Engineering: Projects
Priority: -- → P3
QA Contact: build → release
Summary: [thunderbid] Request a tinderbox setup with debug enabled and not stripped → [thunderbird] Request a tinderbox setup with debug enabled and not stripped
Having the symbols available on the symbol server should help. Also, we dont do this for other projects, because of the disk space issues mentioned in comment#2. Can we close this as WONTFIX?
Symbols sound like a reasonable alternative to me. Do we need separate spinoff bugs for both Linux and Windows Thunderbird symbol hosting, or should we just morph this one?
dmose: Thunderbird Win32 symbols are already available at http://symbols.mozilla.org/thunderbird. The linux symbol server stuff hasn't been turned on, but it will work for Thunderbird as well.
(In reply to comment #7) > dmose: Thunderbird Win32 symbols are already available at > http://symbols.mozilla.org/thunderbird. The linux symbol server stuff hasn't > been turned on, but it will work for Thunderbird as well. When, for Heaven's sake? If it works and just needs turning on, what is the delay?
You know, the limited number of hours in the day.
Over to Mozilla Messaging.
Component: Release Engineering: Future → Release Engineering
Product: mozilla.org → Mozilla Messaging
QA Contact: release → release
This is fixed in comm-central builds. It is possible to download symbols for Mac, Linux and Windows from the Symbol Server. Windows documentation: https://developer.mozilla.org/en/Using_the_Mozilla_symbol_server I couldn't find any Mac/Linux documentation, however I'm told that using: http://people.mozilla.org/~tmielczarek/fetch-symbols.py will pull .dbgsym packages for gdb to use. Therefore marking fixed. Also marking dev-doc-needed as this feels like we need some more documentation on how to debug Mac/Linux.
Keywords: dev-doc-needed
It's enabled for Linux/OS X, and that script will work for Linux, but not for OS X. I had a copy that would work for OS X, but I lost it, apparently. It's fairly similar, I think you just need to download the .dSYM files and put them next to the app binaries. Related, we stopped stripping our Firefox OS X binaries, so our nightly OS X builds have debug symbols as well.
(In reply to comment #12) > Related, we stopped stripping our Firefox OS X binaries, so our nightly OS X > builds have debug symbols as well. Good point, and I'm doing that in bug 518175. So Linux & Windows are already covered, and I think bug 518175 is enough for Mac, hence really resolving as fixed.
Status: NEW → RESOLVED
Closed: 16 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.