On Thu, 06 Jan 2000, Juergen Kreileder wrote:
> You should update your glibc first, the LinuxThreads library is still
> work in progress. E.g. the original glibc-2.1.2 release didn't pass
> sigcontext to user handlers, this was fixed in glibc-2.1.2 CVS tree as
> of 1999/10/24 (this is the version Debian potato uses). glibc-2.1.3
> will fix another bunch of thread problems.
>
Juergen,
In your opinion, is there a combination of glibc, jdk, and gdb stable enough to
debug my native library? I am getting spurious "Program received signal ?,
Unknown signal." in my ddd session's gdb window shortly after the formation
of the three jvm threads. That is, I am not getting to the meat of my problem.
The debug session becomes unusable before I make my first call to the
native lib. A more detailed account of what I have been trying
is found at the end of this message. It is a post I have made to the SuSE
suse-linux-e thread.
I am pretty new to linux devlopment and I know that some of my problems
are no doubt self inflicted, but it strikes me that you must face this
tool compatibility thing every day trying to put out the new jdk builds.
What combination of lib, tool, jdk and os versions would you recommend?
Thanks in advance,
Richard Johnson
**********************************************************************************
A more detailed account of my problem:
I am trying to debug a dynamic native library I have ported from windows that
is used with java 1.2. Unfortunately, I am experiencing "Program received
signal ?, Unknown signal" while trying to create one of the threads in the
java vm.
Searching with google and a search string of "unknown signal gdb linux threads"
produces a number of posts that describe this problem exactly. For
example,
http://www.uwsg.indiana.edu/hypermail/linux/kernel/9909.0/0497.html
is a post of this problem and solution by a SuSE 6.2 user posted
to the linux-kernel list in early September 1999. It suggests rolling
back to gdb-4.17.0.11.
There IS a version of 4.17.0.12 on my 6.2 distribution and unfortunately,
when i use it, I still get this "unknown signal ?" problem when I use it.
It does appear that the linux thread patches have been made to this
version, as I see output in the ddd's gdb window announcing the new threads
as they are created:
Continuing.
[New Thread 2906]
[New Thread 2905]
[New Thread 2907]
Unfrontunately for me, this is followed by:
Program received signal ?, Unknown signal.
[Switching to Thread 2907]
Program received signal ?, Unknown signal.
0x4011cb6e in __sigsuspend (set=0xbf7ffc74) at
../sysdeps/unix/sysv/linux/sigsuspend.c:48
../sysdeps/unix/sysv/linux/sigsuspend.c:48: No such file or directory.
Trying to continue with a "signal 0" or continue just hangs the
ddd/gdb session.
I am going to try the .11 version. I think I have it on the 6.1 cdrom. But I guess
the question is, shouldn't the .12 version on the 6.2 cd work?
----------------------------------------------------------------------
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
