13673 - "apprunner" on HP-UX 10.20 workstation cores

Status: VERIFIED FIXED

(SeaMonkey :: General, defect, P3)

Description

[Jason L. Grace]

apprunner cored with the following gdb stack trace:

#0  0x7a933150 in PL_strcmp () from /work/gnu/mozilla/dist/bin/libplc3.sl
#1  0x7a43e1cc in NSRegisterSelf (aServMgr=0x40005020, path=0x40027040
"rel:libucvlatin.sl") at nsUCvLatinDll.cpp:914
#2  0x7a8da5dc in SelfRegisterDll__23nsNativeComponentLoaderP5nsDllPCc
(this=0x40005d40, dll=0x40008c40,
    registryLocation=0x40027040 "rel:libucvlatin.sl") at
nsNativeComponentLoader.cpp:453
#3  0x7a8db42c in
AutoRegisterComponent__23nsNativeComponentLoaderiP11nsIFileSpecPi
(this=0x40005d40, when=0, component=0x40027020,
    registered=0x7b03b664) at nsNativeComponentLoader.cpp:706
#4  0x7a8d9b40 in
RegisterComponentsInDir__23nsNativeComponentLoaderiP11nsIFileSpec
(this=0x40005d40, when=0, dir=0x4002b220)
    at nsNativeComponentLoader.cpp:288
#5  0x7a8d9558 in
AutoRegisterComponents__23nsNativeComponentLoaderiP11nsIFileSpec
(this=0x40005d40, aWhen=0, aDirectory=0x4002b220)
    at nsNativeComponentLoader.cpp:232
#6  0x7a8d2870 in AutoRegister__22nsComponentManagerImpliP11nsIFileSpec
(this=0x40008080, when=0, inDirSpec=0x0)
    at nsComponentManager.cpp:1945
#7  0x7a8e4b84 in AutoRegister__18nsComponentManageriP11nsIFileSpec (when=0,
directory=0x0) at nsRepository.cpp:196
#8  0xb344 in NS_AutoregisterComponents () at nsSetupRegistry.cpp:89
#9  0xbf6c in NS_SetupRegistry_1 () at nsSetupRegistry.cpp:109
#10 0x989c in main1 (argc=1, argv=0x7b03aeb0) at nsAppRunner.cpp:759
#11 0xa4c0 in main (argc=1, argv=0x7b03aeb0) at nsAppRunner.cpp:859

The viewer app cored while calling PL_strcmp as well.

Comment 1

[Jason L. Grace]

From Jason:

g_Factory's index 12 has the argument passed to PL_strcmp out of range,
according to a more detailed analysis.  First argument our of range, second
argument "Unicode" (ok).  Maybe it got corrupted during the "data = &gfa..[i]"
part earlier in the module?

Comment 2

[J Shane Culpepper]

Fixed.  please refer to bug number 13779 which is the same.

Comment 3

[J Shane Culpepper]

Fixed.  please refer to bug number 13779 which is the same.

Comment 4

[leger]

Marking Verified.