Closed
Bug 27103
Opened 25 years ago
Closed 25 years ago
immediate crash on startup
Categories
(SeaMonkey :: General, defect, P3)
Tracking
(Not tracked)
VERIFIED
WORKSFORME
People
(Reporter: godot, Assigned: leger)
Details
(Keywords: crash)
Linux 2.2.14, Dual P-III 450, Single P-III; mozilla.cvs (09.02.2000); gcc-2.95.2
Linux 2.2.13, Dual P-III 500; source snapshot (mid january); egcs-1.1.2
all systems basically SuSE 6.3, all requirements (according to mozilla.org) met.
(there is a report of EXACTLY the same crash about mozilla.cvs built on
Redhat 6.x)
- fresh build, no stale *.o/*.so files lying around
Starting mozilla repeatably crashes within its startup phase:
(gdb) run
Starting program: /data/mirror-cvs/mozilla/dist/bin/./mozilla-bin
nsNativeComponentLoader: autoregistering begins.
Program received signal SIGSEGV, Segmentation fault.
0x40179d48 in nsNativeComponentLoader::AutoRegisterComponent (this=0x805a658,
when=0, component=0x805f170, registered=0xbffff088) at
nsNativeComponentLoader.cpp:732
(gdb) bt
#0 0x40179d48 in nsNativeComponentLoader::AutoRegisterComponent
(this=0x805a658, when=0, component=0x805f170, registered=0xbffff088) at
nsNativeComponentLoader.cpp:732
#1 0x40178ba6 in nsNativeComponentLoader::RegisterComponentsInDir
(this=0x805a658, when=0, dir=0x805dff8) at nsNativeComponentLoader.cpp:286
#2 0x401788a8 in nsNativeComponentLoader::AutoRegisterComponents
(this=0x805a658, aWhen=0, aDirectory=0x805dff8) at
nsNativeComponentLoader.cpp:226
#3 0x40175f48 in nsComponentManagerImpl::AutoRegister (this=0x80597c0, when=0,
inDirSpec=0x0) at nsComponentManager.cpp:2065
#4 0x4017ddfb in nsComponentManager::AutoRegister (when=0, directory=0x0) at
nsRepository.cpp:200
#5 0x804e2e2 in NS_AutoregisterComponents () at nsSetupRegistry.cpp:82
#6 0x804f827 in NS_SetupRegistry_1 () at nsSetupRegistry.cpp:102
#7 0x804d212 in main1 (argc=1, argv=0xbffff4a4, splashScreen=0x0) at
nsAppRunner.cpp:478
#8 0x804e0d7 in main (argc=1, argv=0xbffff4a4) at nsAppRunner.cpp:677
(gdb) p mCompMgr
$1 = (nsIComponentManager *) 0x0
^^^
I do have this problem all the way since about mid december, blocking any
development or testing for me. No matter whether I use mozilla.cvs or a
source snapshot. Used "configure" as well as "configure --disable-mailnews"
There are a couple of bugs with exactly the same stack trace. See the tips
in <a href=http://bugzilla.mozilla.org/show_bug.cgi?id=15934>bug 15934</a>:
> ------- Additional Comments From dp@netscape.com 1999-10-14 08:38 -------
> Are you sure you deleted ~/.mozilla/registry
>
> The format of that changed in M10. Could you try that.
>
> Also delete bin/component.reg
Let me know if that doesn't work for you.
Frank says:
>27103 is another bug.
>It persists even when deleting component.reg (or even whole ~/.mozilla)
>
>Frank
here's dp's other suggestion in that bug:
>------- Additional Comments From dp@netscape.com 1999-10-11 11:32 -------
>Do you have funny characters in the path where you installed M10. Also could
>you give me a log from xpcom. Here is how you get it:
>
>setenv NSPR_LOG_MODULES nsComponentManager:5
>setenv NSPR_LOG_FILE xpcom.log
> Run viewer/apprunner whichever you see the crash in. Add the file xpcom.log
> as an attachment to the bug.
This does not occur with todays FEb 14 build. Please go get the latest build
and try this out. http://www.mozilla.org/binaries.html
Marking Verified/WorksForme.
Status: NEW → RESOLVED
Closed: 25 years ago
Resolution: --- → WORKSFORME
Updated•20 years ago
|
Product: Browser → Seamonkey
You need to log in
before you can comment on or make changes to this bug.
Description
•