Open Bug 932029 Opened 11 years ago Updated 2 years ago

missing file / line number info for NSPR functions in libnss3.dylib frames in crash stacks

Categories

(Firefox Build System :: General, defect)

x86_64
Linux
defect

Tracking

(Not tracked)

People

(Reporter: karlt, Unassigned)

Details

(Keywords: regression)

This bug is visible in test logs and on crash-stats.

See for example these logs on 10.6 an 10.7
https://tbpl.mozilla.org/php/getParsedLog.php?id=29591635&full=1&branch=mozilla-inbound#error1
https://tbpl.mozilla.org/php/getParsedLog.php?id=29590964&full=1&branch=fx-team#error1

  2  libnss3.dylib!_PR_CreateThread + 0x248
     rbx = 0x0000000000000000   r14 = 0x0000000000000000
     r15 = 0x0000000000000001   rip = 0x00000001005140e9
     rsp = 0x000000011e9808e0   rbp = 0x000000011e980980
     Found by: call frame info

  5  libnss3.dylib!PR_CreateThread + 0x1a
     rip = 0x0000000100513e8b   rsp = 0x000000011e980990
     rbp = 0x000000011e9809a0
     Found by: stack scanning

 19  libnss3.dylib!_pt_root + 0xca
     rbx = 0x000000011cb554b0   r12 = 0x0000000000000000
     r13 = 0x0000000000008e03   r14 = 0x0000000000000000
     r15 = 0x000000011cb554b0   rip = 0x000000010051534b
     rsp = 0x000000011e980ef0   rbp = 0x000000011e980f10
     Found by: call frame info

Don't know whether this is specific to NSPR or all of libnss3.

https://tbpl.mozilla.org/php/getParsedLog.php?id=29592652&tree=Mozilla-Inbound
shows nsprpub/pr/src/pthreads/ptthread.c compiled with -g

See also bp-ebdad21c-f8ab-4835-9179-440552131027

Crash reports from ESR17 have file and line number info for libnspr4.dylib.
e.g. bp-8807eb79-3aa5-4b8e-be97-29d4b2131028

I wonder whether this might be related to merging NSPR into libnss3.dylib.
Seems likely, yeah.
If the object files are built with -g, there is no reason that the debug info wouldn't be available.
I guess we need to check the symbol files (both breakpad's and dwarfs) from the symbol server.
Product: Core → Firefox Build System
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.