On Mon, 03 Jan 2000, you wrote:
> richard johnson wrote:
> >
> > Program received signal ?, Unknown signal.
> > 0x4012eb6e in __sigsuspend (set=0xbffff2a8) at
>../sysdeps/unix/sysv/linux/sigsuspend.c:48
> > 48 ../sysdeps/unix/sysv/linux/sigsuspend.c: No such file or directory.
>
> The "no such file or directory" just means that gdb can't find the
> source file in order to display source lines. The real problem here is
> the unknown signal, which I don't know how to address. Does it only die
> this early when running under the debugger?
Yes. It appears to only die this early when the debugger is in use.
What do you make of the line in the stack trace
in sysThreadCreate ...at
../../../../../src/linux/hpi/native_threads/src/threads_md.c:403
I noticed that this is a native threads method, yet I was running green threads
when this happened. Does green threads have native threads for the threads
beside main (SIGQUIT and ?)?
>
> Have you tried the Blackdown or Inprise JDK1.2.2 - those will give you
> two additional sample points.
>
First, I am going to re-check my installation to see if I have the right version of
the jdk 1.2 pre2
installed. If this checks, I plan to install the debug addendum for 1.2 and see if
there is more information about what is happening by running/studying the debug vm.
My next attempt will be with the 1.2.2 from Inprise as it will not
require a new glib version ... as I recollect. Installing a new glib is somewhat
messy
from what I have read. Then I might upgrade my kernel to SuSE 6.3 which I believe
has the appropriate glibc for Blackdown 1.2.2.
If I come up with something I'll post the list so that maybe someone else won't
go through this. Thanks again for your help.
Rich
>
> > I want to thank you for your help with the debugging of the my
> > unloaded native lib. The use of the LD_PRELOAD allowed me
> > to set the breakpoint in my native library (after as you suggested,
> > setting the breakpoint in main() and stopping there). I bought
> > your book too!
> >
> > Unfortunately, I am not reaching this breakpoint instead dying
> > during jvm initialization trying to create the SIGQUIT handler. I get the
>following
> > message in the gdb window of my ddd debugger session:
> >
> > Program received signal ?, Unknown signal.
> > 0x4012eb6e in __sigsuspend (set=0xbffff2a8) at
>../sysdeps/unix/sysv/linux/sigsuspend.c:48
> > 48 ../sysdeps/unix/sysv/linux/sigsuspend.c: No such file or directory.
> >
> > The call stack looks like this:
> >
> > in __sigsuspend ... at ../sysdeps/unix/sysv/linux/sigsuspend.c:48
> > in __pthread_create_2_1 ...at restart.h:32
> > in sysThreadCreate ...at
>../../../../../src/linux/hpi/native_threads/src/threads_md.c:403
> > in threadCreate ... at ../../../../src/share/javavm/runtime/threads.c:167
> > in createSystemThread "SIGQUIT handler" ...at
>../../../../src/share/javavm/runtime/threads.c:506
> > in InitializeSignals ...at ../../../../src/linux/javavm/runtime/signals_md.c:548
> > in InitializeJavaVM ...at ../../../../src/linux/javavm/runtime/javai.c:847
> > in JNI_CreateJavaVM ...at ../../../../../src/share/javavm/runtime/jni.c:3263
> > in InitializeJVM ...at ../../../../../src/share/bin/java.c:467
> > in main ...at ../../../../../src/share/bin/java.c:173
> >
> > It looks like I am missing some file or have a bad path somewhere that causes the
> > "SIGQUIT handler" to abort. Does anyone know what file or directory is being
> > sought? What do I do next? Should I install the debug version? Is there
>documentation
> > available that describe the jvm initialization?
> >
> > I am using SuSE 6.2 (glibc2.1), blackdown jdk1.2 pre release v2`
> > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
----------------------------------------------------------------------
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
