Subj : Re: spider monkey core dump in js_EmitTree
To   : Mahapatra Anindita <Anindita.Mahapatra@comverse.com>
From : Brendan Eich <brendan@meer.net>
Date : Wed Mar 19 2003 06:20 pm

Mahapatra Anindita wrote:

>I have a threadsafe, optimized Linux version of libjs.so
>I'm executing a vxml script, the in-house vxml interpreter passes requests
>to the script engine to evaluate expressions
>In this particular case, while an expression is being evaluated, the
>executable gives a segmentation fault & running gdb on the core file yields:
>
>  #0  0x402c3447 in js_EmitTree ()
>   from /vob/ThirdParty/ScriptEngine/SpiderMonkey/linux/lib/libjs.so 
>

First, get a fresh version of the engine.  I can't debug downrev 
versions.  cvs.mozilla.org trunk pull and build is best, 1.5 RC5 is 
debuggable.

Second, how about a stack backtrace, line number in jsemit.c where the 
crash occurs, local variable values, at the least?  It's not useful to 
have a testcase that can't be used outside of your embedding, when with 
a debuggerattached or a core file post-mortem debug session, you should 
be able to detail the skidmarks.

/be

.