This is the mail archive of the
java@gcc.gnu.org
mailing list for the Java project.
Re: Can't debug my xlib changes because gdb gets SIGTRAP in __sigsuspendvia _Jv_ThreadWait
- From: Jeff Sturm <jsturm at one-point dot com>
- To: Scott Gilbertson <scottg at mantatest dot com>
- Cc: java at gcc dot gnu dot org
- Date: Sun, 1 Dec 2002 13:09:16 -0500 (EST)
- Subject: Re: Can't debug my xlib changes because gdb gets SIGTRAP in __sigsuspendvia _Jv_ThreadWait
On Fri, 29 Nov 2002, Scott Gilbertson wrote:
> (gdb) break XFillPolygon
> Breakpoint 1 at 0x8051c16
> (gdb) run
> Starting program: /home/scott/mts5000/java/mts5000.bin PC SILENT
>
> Program received signal SIGTRAP, Trace/breakpoint trap.
SIGTRAP indicates that a breakpoint is reached, but it should have been
properly handled by gdb. Gdb needs to cooperate with linuxthreads to
debug threaded programs correctly. Since it isn't working for you I'd
guess something broke in glibc, gdb or both.
I don't have Red Hat 8.0. Perhaps someone who does can say whether gdb
is working for them. I've had good results with RH 7.x and a hand-built
toolchain including gdb.
Several things you might try:
- File a bug report with Red Hat
- Downgrade to 7.x
- Build a custom gcj toolchain with binutils, gdb and glibc (the latter
can be tricky).
Jeff