Re: [Sablevm-developer] Found deadlock in Class.getConstructor(Class[]).newInstance(Objects[])
Brought to you by:
egagnon
From: Clemens E. <lin...@we...> - 2004-04-15 17:16:27
|
Hi Etienne! > SableVM will dump a stack trace during execution when you cause a SIGQUIT > signal. On most systems you do this by pressing Ctrl-\ (Control key > and "\" > key together). It gives much more information than a simple gdb stack > dump > which does not tell us about the content of the Java stack. I've a german keyboard, where "/" is generated by pressing the "big"-key (=write letters big) and the "7"-key. Pressing STRG+7 and Strg+big+7 don't work. Any Ideas howto generate SIGQUIT on a german keyboard? (Strg+c doesn't print out anything, it just quits sablevm). > I you have time, it would be grat if you also sent a minimal complete > piece > of code that I could simply "compile and run" to exhibit the problem. Currently I'm really very stressed, maybe I can find some time.. lg Linuxhippy |