Closed
Bug 204147
Opened 22 years ago
Closed 13 years ago
Stack overflow with PRLogging, PR_Lock <=> PR_LogPrint
Categories
(NSPR :: NSPR, defect)
Tracking
(Not tracked)
RESOLVED
INCOMPLETE
People
(Reporter: timeless, Assigned: wtc)
Details
(Keywords: crash)
steps:
patch xpcom so that it calls PR_Cleanup
export NSPR_LOG_MODULES=nsComponentManager:5
./run-mozilla.sh ./xpcshell
quit()
xpcshell crashed with a stack overflow:
#9555 0x40281d75 in PR_LogPrint (
fmt=0x8058288 "Assertion failure: lock != NULL, at /mnt/ibm/mozhack/mozilla/nsprpub/pr/src/pthreads/ptsynch.
c:189\n") at /mnt/ibm/mozhack/mozilla/nsprpub/pr/src/io/prlog.c:445
#9556 0x40281f62 in PR_Assert (s=0x402b0bfc "lock != NULL",
file=0x402b0b20 "/mnt/ibm/mozhack/mozilla/nsprpub/pr/src/pthreads/ptsynch.c", ln=189)
at /mnt/ibm/mozhack/mozilla/nsprpub/pr/src/io/prlog.c:514
#9557 0x4029beb2 in PR_Lock (lock=0x0) at /mnt/ibm/mozhack/mozilla/nsprpub/pr/src/pthreads/ptsynch.c:189
#9558 0x40281d75 in PR_LogPrint (fmt=0x402459df "nsIThread %p exited\n")
at /mnt/ibm/mozhack/mozilla/nsprpub/pr/src/io/prlog.c:445
#9559 0x401d6893 in nsThread::Exit (arg=0x8051fb0) at /mnt/ibm/mozhack/mozilla/xpcom/threads/nsThread.cpp:152
#9560 0x402871f5 in _PR_DestroyThreadPrivate (self=0x8051258)
at /mnt/ibm/mozhack/mozilla/nsprpub/pr/src/threads/prtpd.c:260
#9561 0x402a58e2 in _pt_thread_death (arg=0x8051258)
at /mnt/ibm/mozhack/mozilla/nsprpub/pr/src/pthreads/ptthread.c:799
#9562 0x402a5d92 in PR_Cleanup () at /mnt/ibm/mozhack/mozilla/nsprpub/pr/src/pthreads/ptthread.c:943
#9563 0x40153294 in NS_ShutdownXPCOM (servMgr=0x0) at /mnt/ibm/mozhack/mozilla/xpcom/build/nsXPComInit.cpp:786
#9564 0x0804ccdb in main (argc=0, argv=0xbffff818)
at /mnt/ibm/mozhack/mozilla/js/src/xpconnect/shell/xpcshell.cpp:1010
#9565 0x4036217d in __libc_start_main () from /lib/libc.so.6
(
Assignee | ||
Updated•22 years ago
|
Status: UNCONFIRMED → NEW
Ever confirmed: true
Updated•18 years ago
|
QA Contact: wtchang → nspr
![]() |
||
Comment 1•13 years ago
|
||
This bug has no information on current versions and no clear lead as to what the crashes that it tracks are. This should either be updated with current info and reopened or new bugs be filed on concrete actions/crashes on current code.
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → INCOMPLETE
You need to log in
before you can comment on or make changes to this bug.
Description
•