It appears to be the same thing for tcc and lcc on linux. The nearest I can tell, the value stuffed into struct_val in Parrot_NCI_set_string_keyed is somehow not a valid PObj- dereferencing its "obj" member seems to blow things up.
It stomps all over the stack somehow, and I don't have much debugger mojo. Plus, building with "-g" makes the problem go away. Bah. --Josh At 14:09 on 01/20/2003 EST, Dan Sugalski <[EMAIL PROTECTED]> wrote: > Rather badly, actually. All the tests that involve parrot currently > segfault in the NCI mark routine. At least on OS X, I'm not sure > about other platforms. > -- > Dan > > --------------------------------------"it's like this"------------------- > Dan Sugalski even samurai > [EMAIL PROTECTED] have teddy bears and even > teddy bears get drunk
