184260 - crash & core dump on Solaris/Intel

Status: VERIFIED DUPLICATE of bug 149461

(Core :: XPConnect, defect)

Description

[Nathan Kunkee]

User-Agent:       Mozilla/4.76 [en] (X11; U; SunOS 5.8 i86pc)
Build Identifier: cvs checkout of MOZILLA_1_2_1_RELEASE dated about 4 days ago

screen output:

*** Registering nsUniversalCharDetModule components (all right -- a generic
module!)
*** Registering nsTypeAheadFind components (all right -- a generic module!)
nsNativeComponentLoader: autoregistering succeeded
WARNING: XPConnect was passed aJSContext from a foreign JSRuntime!, file
nsXPConnect.cpp, line 302
JS Component Loader: ERRORSegmentation Fault - core dumped


Reproducible: Always

Steps to Reproduce:
1. build on solaris/intel. configure with pthreads, gtk, without mail, ldap, or
installer. also show up without debug or tests
2.after build cycle, run-mozilla.sh from dist/bin
3.core dump

Actual Results:  
see details. no windows were mapped.

Expected Results:  
load.

Comment 1

[Nathan Kunkee]

Attachment: screen output and stack trace

From the description, this may be similar to bug #173022, except the stack
trace is different.

Comment 2

[Phil Schwartau]

---> XPConnect

Comment 3

[David Bradley]

Can you run TestXPTCInvoke and does it succeed?

Comment 4

[Nathan Kunkee]

No, TestXPTCInvoke does not complete. 
--------------
$ LD_LIBRARY_PATH=/local/mozilla/dist/bin:/local/mozilla/dist/lib
./TestXPTCInvoke                                  <

calling direct:
        1 + 1 = 2
        1L + 1L = 2
        2 * 2 = 4
        2L * 2L = 4
        1 + 2 + 3 + 4 + 5 + 6 + 7 + 8 + 9 + 10 = 55
        1 + 2 = 3.000000f
        1 + 2 + 3 + 4 + 5 + 6 + 7 + 8 + 9 + 10 = 55.000000
        1 + 2 + 3 + 4 + 5 + 6 + 7 + 8 + 9 + 10 = 55.000000f
        1 + 2 + 3 + 4 + 5 + 6 + 7 + 8 + 9 + 10 + 11 + 12 + 13 + 14 +1 15 + 16 +
17 + 18 + 19 + 20 = 210.000000f
        moo cow = milk
calling via invoke:
Segmentation Fault(coredump)
----------------------
I have the means to load this in a debugger. What else can I do to help?

Comment 5

[timeless]

*** This bug has been marked as a duplicate of 149461 ***

Comment 6

[Phil Schwartau]

Marking Verified Duplicate, but deferring to the developers 
on this one. The stack trace given in this bug is not the same
as the one given in  bug 173022 or bug 149461.

Nathan: you have been cc'ed on bug 149461 so you can follow
progress on this issue. If that bug is ever fixed, but this
bug remains a problem, please reopen this one; thanks - 

Comment 7

[Nathan Kunkee]

I have applied the patch given on bug 149461, and established (to my
satisfaction) that is works. I have built a debug and release version and have
had no trouble.