This is the mail archive of the
java@gcc.gnu.org
mailing list for the Java project.
RE: hanging
- From: "Boehm, Hans" <hans dot boehm at hp dot com>
- To: "Fabio Roger" <fabioroger at gmail dot com>, <java at gcc dot gnu dot org>
- Date: Mon, 28 Feb 2005 11:01:49 -0800
- Subject: RE: hanging
Can you get stack traces for the hung threads? (I have no mingw
experience.) In my experience on other platforms,
nothing is above suspicion for this sort of a problem. But given
stack traces and some idea what each thread is waiting for, it's
usually not too hard to debug.
There are some general hints about GC debugging at
http://www.hpl.hp.com/personal/Hans_Boehm/gc/debugging.html
but I think that's not very applicable to this problem, at
least not yet.
Hans
> -----Original Message-----
> From: java-owner@gcc.gnu.org [mailto:java-owner@gcc.gnu.org]
> On Behalf Of Fabio Roger
> Sent: Monday, February 28, 2005 4:01 AM
> To: java@gcc.gnu.org
> Subject: hanging
>
>
> hi all,
>
> I need help on how to debug this particular situation:
>
> I have an application with lots of threads and native methods
> for hardware handling and everything works fine.. all
> compiled to native with gcj 3.4.0 from
> http://www.thisiscool.com/gcc_mingw.htm:
>
> Configured with: /datal/gcc/gcc/configure --
> prefix=/datal/gcc/build/wingcc --build=i686-pc-linux-gnu
> --host=i686-pc- mingw32 --target=i686-pc-mingw32
> --enable-languages=c,c++,java --with- gcc --with-gnu-as
> --with-gnu-ld --with-as=i686-pc-mingw32-as --with-
> ld=i686-pc-mingw32-ld --enable-threads=win32 --disable-nls
> --disable- win32-registry --disable-shared --disable-debug
> --without-newlib -- enable-libgcj --disable-java-awt
> --without-x --enable-java-gc=boehm -- disable-libgcj-debug
> --enable-interpreter --enable-hash-synchronization
> --enable-sjlj-exceptions --enable-libgcj-multifile
> --enable-libgcj- mingw-osapi=ansi Thread model: win32 gcc
> version 3.4.0 20040316 (prerelease)
>
>
> all works fine.. BUT sometimes (like once a day) the thing
> just hangs.. not even the threads waiting for tcp requests,
> replies.. (but the OS is still ok)
>
> my issue is.. I have no idea what "might" be going wrong..
> and no idea how to debug the thing either.. no error msg
> comes up.. no exception thrown, nothing.. it just hangs..
>
> any idea of what kind of thing could it be or any direction?
>
> btw, how to debug the garbage collector in a gcj-compiled executable?
>
> thanks!
>
> Fabio Roger
>
>
>