Closed Bug 26708 Opened 25 years ago Closed 25 years ago

BSD: crash on startup in xptcall stuff

Categories

(Core :: XPConnect, defect, P3)

x86
FreeBSD
defect

Tracking

()

RESOLVED FIXED

People

(Reporter: daeron, Assigned: jband_mozilla)

Details

(Keywords: crash)

On my FreeBSD-4.0-CURRENT system I have been unable to successfully startup mozilla-builds for several days now. (builds are from CVS-tree) .//run-mozilla.sh ./mozilla-bin MOZILLA_FIVE_HOME=/usr/local/src/mozilla/FreeBSD_4.0-CURRENT_clobber/mozilla/obj-i386-unknown-freebsd4.0/dist/bin LD_LIBRARY_PATH=/usr/local/src/mozilla/FreeBSD_4.0-CURRENT_clobber/mozilla/obj-i386-unknown-freebsd4.0/dist/bin:/home/daeron/GNUstep/Libraries/ix86/freebsdelf4.0/gnu-gnu-gnu-xgps:/home/daeron/GNUstep/Libraries/ix86/freebsdelf4.0:/usr/GNUstep/Local/Libraries/ix86/freebsdelf4.0/gnu-gnu-gnu-xgps:/usr/GNUstep/Local/Libraries/ix86/freebsdelf4.0:/usr/GNUstep/Libraries/ix86/freebsdelf4.0/gnu-gnu-gnu-xgps:/usr/GNUstep/Libraries/ix86/freebsdelf4.0 SHLIB_PATH=/usr/local/src/mozilla/FreeBSD_4.0-CURRENT_clobber/mozilla/obj-i386-unknown-freebsd4.0/dist/bin LIBPATH=/usr/local/src/mozilla/FreeBSD_4.0-CURRENT_clobber/mozilla/obj-i386-unknown-freebsd4.0/dist/bin MOZ_PROGRAM=./mozilla-bin MOZ_TOOLKIT= moz_debug=0 moz_debugger= JS Component Loader: ERROR /usr/local/src/mozilla/FreeBSD_4.0-CURRENT_clobber/mozilla/obj-i386-unknown-freebsd4.0/dist/bin/components/nsCategoryManager.js:27 TypeError: Components.interfaces has no properties Segmentation fault - core dumped
Component: Browser-General → XPCOM
Hi, daeron. Can you provide a stack trace?
Component: XPCOM → XPConnect
(gdb) bt #0 0x0 in ?? () #1 0x281ea14f in XPTC_InvokeByIndex (that=0x816eb60, methodIndex=4, paramCount=1, params=0xbfbfd6c4) at ../../../../../../../xpcom/reflect/xptcall/src/md/unix/xptcinvoke_unixish_x86.cpp:159 #2 0x285ac1b4 in nsXPCWrappedNativeClass::CallWrappedMethod (this=0x816cd80, cx=0x806d400, wrapper=0x816cdc0, desc=0x8166628, callMode=CALL_GETTER, argc=0, argv=0x0, vp=0xbfbfe0bc) at ../../../../../js/src/xpconnect/src/xpcwrappednativeclass.cpp:898 #3 0x285b6224 in nsXPCWrappedNativeClass::GetAttributeAsJSVal (this=0x816cd80, cx=0x806d400, wrapper=0x816cdc0, desc=0x8166628, vp=0xbfbfe0bc) at ../../../../../js/src/xpconnect/src/xpcprivate.h:870 #4 0x285ae4e0 in WrappedNative_GetProperty (cx=0x806d400, obj=0x815bfc8, id=135720000, vp=0xbfbfe0bc) at ../../../../../js/src/xpconnect/src/xpcwrappednativejsops.cpp:244 #5 0x280f53c1 in js_Interpret (cx=0x806d400, result=0xbfbfe1b0) at ../../../js/src/jsinterp.c:2229 #6 0x280ec95e in js_Invoke (cx=0x806d400, argc=1, flags=0) at ../../../js/src/jsinterp.c:681 #7 0x280f63cf in js_Interpret (cx=0x806d400, result=0xbfbfecb0) at ../../../js/src/jsinterp.c:2273 #8 0x280ece89 in js_Execute (cx=0x806d400, chain=0x815c1e0, script=0x8166e00, fun=0x0, down=0x0, special=0, result=0xbfbfecb0) at ../../../js/src/jsinterp.c:836 #9 0x280c6e11 in JS_ExecuteScript (cx=0x806d400, obj=0x815c1e0, script=0x8166e00, rval=0xbfbfecb0) at ../../../js/src/jsapi.c:2652 #10 0x285660ac in mozJSComponentLoader::GlobalForLocation (this=0x8090900, aLocation=0x80d13b0 "rel:nsSample.js", component=0x8090980) at ../../../../../js/src/xpconnect/loader/mozJSComponentLoader.cpp:689 #11 0x28565a0c in mozJSComponentLoader::ModuleForLocation (this=0x8090900, registryLocation=0x80d13b0 "rel:nsSample.js", component=0x8090980) at ../../../../../js/src/xpconnect/loader/mozJSComponentLoader.cpp:563 #12 0x28565697 in mozJSComponentLoader::AttemptRegistration (this=0x8090900, component=0x8090980, deferred=0) at ../../../../../js/src/xpconnect/loader/mozJSComponentLoader.cpp:475 #13 0x2856556b in mozJSComponentLoader::AutoRegisterComponent (this=0x8090900, when=0, component=0x8090980, registered=0xbfbfeee8) at ../../../../../js/src/xpconnect/loader/mozJSComponentLoader.cpp:445 #14 0x28564e15 in mozJSComponentLoader::RegisterComponentsInDir (this=0x8090900, when=0, dir=0x8090700) at ../../../../../js/src/xpconnect/loader/mozJSComponentLoader.cpp:331 #15 0x28564b70 in mozJSComponentLoader::AutoRegisterComponents (this=0x8090900, when=0, aDirectory=0x8090700) at ../../../../../js/src/xpconnect/loader/mozJSComponentLoader.cpp:287 #16 0x281c9bfc in AutoRegister_enumerate (key=0x80d2c00, aData=0x8090900, aClosure=0xbfbff0e0) at ../../../xpcom/components/nsComponentManager.cpp:2026 #17 0x2818fd9d in _hashEnumerate (he=0x80d1380, i=0, arg=0xbfbff01c) at ../../../xpcom/ds/nsHashtable.cpp:89 #18 0x28246a1c in PL_HashTableEnumerateEntries (ht=0x805f360, f=0x2818fd64 <_hashEnumerate(PLHashEntry *, int, void *)>, arg=0xbfbff01c) at plhash.c:368 #19 0x281902f3 in nsHashtable::Enumerate (this=0x806c320, aEnumFunc=0x281c9b6c <AutoRegister_enumerate(nsHashKey *, void *, void *)>, closure=0xbfbff0e0) at ../../../xpcom/ds/nsHashtable.cpp:218 #20 0x281ca511 in nsComponentManagerImpl::AutoRegister (this=0x806a880, when=0, inDirSpec=0x0) at ../../../xpcom/components/nsComponentManager.cpp:2113 #21 0x281d1c2c in nsComponentManager::AutoRegister (when=0, directory=0x0) at ../../../xpcom/components/nsRepository.cpp:200 #22 0x804ef03 in NS_AutoregisterComponents () at ../../../xpfe/bootstrap/nsSetupRegistry.cpp:82 #23 0x80504b0 in NS_SetupRegistry_1 () at ../../../xpfe/bootstrap/nsSetupRegistry.cpp:102 #24 0x804dc4c in main1 (argc=1, argv=0xbfbff428, splashScreen=0x0) at ../../../xpfe/bootstrap/nsAppRunner.cpp:594 #25 0x804ec3e in main (argc=1, argv=0xbfbff428) at ../../../xpfe/bootstrap/nsAppRunner.cpp:789 #26 0x804bd4d in _start ()
thanks, daeron
Assignee: leger → jband
QA Contact: cbegle → rginda
Summary: Mozilla doesn't startup any longer → BSD: crash on startup in
left a word out of the summary
Summary: BSD: crash on startup in → BSD: crash on startup in xptcall stuff
As far as I can tell from the current startup ... the XPTCall stuff looks fixed now ... It seems the registering of all the modules passes through properly. I cannot say for sure though as there seems to be a different bug that crashes Startup now. I'll try to get back to this later.
I posted a New BUG# 27064 for the startup-crash I am experiencing now, since I seriously think they are not related. As far as I can tell ... the XPTCall issues are solved. but i can't tell for sure until I have a resolution for #27064
Putting crash in the keyword field.
Keywords: crash
Severity: major → critical
daeron, I'm marking this fixed. It sounds like it was fixed by... /cvsroot/mozilla/xpcom/reflect/xptcall/src/md/unix/xptc_platforms_unixish_x86.h rev. 1.5 That worked for the submitter of that patch. If this turns out not to be the case then please reopen this bug. If you become more confident that this is fixed then please mark this verified. Thanks, John.
Status: NEW → RESOLVED
Closed: 25 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.