On 2003-11-10 08:52:24 -0500, Kevin.Hendricks wrote: > Not on YellowDog Linux it is not. You really should not have problem > interfacing gcc 3.3.2 with gcc 3.2.2 with C++ code since others have > reproted success.
OK. So, how do you explain the following crash? Document http://www.barbery.net/anagram/ loaded successfully SIGSEGV 11* segmentation violation si_signo [11]: SIGSEGV 11* segmentation violation si_errno [0]: Success si_code [196609]: unknown siginfo stackpointer=0x36fc4cbc Full thread dump Classic VM (Blackdown-1.3.1-02d-FCS, native threads): "thread applet-anagram.class" (TID:0x30cbf680, sys_thread_t:0x10433178, state:R, native ID:0x4400f) prio=4 at sun.awt.motif.MChoicePeer.pReshape(Native Method) [...] On the blackdown site, similar crashes were reported as JDK bugs: http://www.blackdown.org/cgi-bin/jdk/incoming?id=2664 http://www.blackdown.org/cgi-bin/jdk/incoming?id=2747 Or is it a libc bug? I have libc6 2.3.2-9. -- Vincent Lefèvre <[EMAIL PROTECTED]> - Web: <http://www.vinc17.org/> - 100% validated (X)HTML - Acorn Risc PC, Yellow Pig 17, Championnat International des Jeux Mathématiques et Logiques, TETRHEX, etc. Work: CR INRIA - computer arithmetic / SPACES project at LORIA
