This is the mail archive of the
java@gcc.gnu.org
mailing list for the Java project.
Re: GCJ application runs not too bad with shared libs, but crasheswith static libs
- From: "Scott Gilbertson" <scottg at mantatest dot com>
- To: "Jeff Sturm" <jsturm at one-point dot com>
- Cc: <java at gcc dot gnu dot org>
- Date: Thu, 21 Nov 2002 12:50:48 -0500
- Subject: Re: GCJ application runs not too bad with shared libs, but crasheswith static libs
- References: <Pine.LNX.4.44.0211202144430.15358-100000@ops2.one-point.com>
> On Wed, 20 Nov 2002, Scott Gilbertson wrote:
> > (gdb) run
> > Starting program: /home/scott/mts5000/java/mts5000.bin PC
> > ... lots of application-generated stuff...
> > Program received signal SIGABRT, Aborted.
> > 0x0817b8e4 in __libc_write ()
> > (gdb) where
> > #0 0x0817b8e4 in __libc_write ()
>
> What are other threads doing? I doubt that write() can trigger a
> SIGABRT. More likely, this thread is waiting for I/O while some other
> thread caused the abort.
>
> Jeff
That's my guess too, but "info threads" doesn't give any output in gdb.
Since I'm new to linux debugging I assume I'm doing something wrong.