Closed Bug 282397 Opened 20 years ago Closed 20 years ago

MozillaTrunk symbols missing for Linux builds since mid-January

Categories

(Core Graveyard :: Talkback Client, defect)

Product:
Core Graveyard
Component:
Talkback Client
Platform:
x86
Linux
Type:
defect
Priority:
Not set
Severity:
critical

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: jay, Assigned: chase)

Details

Looks like we haven't been getting symbols uploaded for Linux seamonkey builds since January. Chase is looking into it.
nominating for blocking1.8b
Flags: blocking1.8b?
QA Contact: chofmann → jay
see Bug 207136 Talkback data no longer reports register values for Windows builds Bug 207136 Comment #3 From Shiva Thirumazhusai 2003-05-27 09:10 PST It is a known problem.
Herman: I'm pretty sure that other bug is referring to the register info in the detailed Talkback reports (which can now only be viewed by internal Mozilla staff). This bug is for a server related issue that is causing us to get unresolved stack frames in the Talkback reports everyone is able to lookup at http://talkback-public.mozilla.org. We simply need to figure out why the symbol info for Linux Seamonkey builds are not being uploaded to our Talkback incident processing server (so we can get nice looking stacks with functions, filenames, and line numbers).
yep. gotta have this.
Flags: blocking1.8b? → blocking1.8b+
OS: Windows XP → Linux
But the stack does not make sense. For example, 'ComputeBackgroundAnchorPoint' does not have a call to 'RenderSide'.
Talkback stacks don't always make sense...but the symbols are now there for Linux builds, so marking this fixed.
Status: NEW → RESOLVED
Closed: 20 years ago
Resolution: --- → FIXED
(In reply to comment #7) > Talkback stacks don't always make sense... I am aware of that. It is unusual that the entire stack is unuseable though, in my experience there are usually something at the beginning that does make sense, like main() for example. The 5-6 latest talkback data I have submitted are all unuseable (the entire stack does not make sense), that seems unlikely... Could you please verify that symbols are working on Linux by manually doing a crash using a abort() or something that does not mess up the stack. Thanks.
You've tried a build in the last few days?
(In reply to comment #8) > I am aware of that. It is unusual that the entire stack is unuseable though, > in my experience there are usually something at the beginning that does make > sense, like main() for example. The 5-6 latest talkback data I have submitted > are all unuseable (the entire stack does not make sense), that seems unlikely... I think the GTK1 and GTK2 SeaMonkey builds are occasionally smashing each other's symbols. This happens if they end up with the same build ID (since they're both Linux with the same product and version). We'll probably need to file a new bug for that if it turns out to be the case.
(In reply to comment #10) > I think the GTK1 and GTK2 SeaMonkey builds are occasionally smashing each > other's symbols. This happens if they end up with the same build ID Yes, that is the case - filed bug 282863.
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.