This is the mail archive of the
java@gcc.gnu.org
mailing list for the Java project.
SV: GCJ 3.3 garbage collection live-lock(conjencture) and GDB for iditos and
- From: Andrew Haley <aph at redhat dot com>
- To: Øyvind Harboe <oyvind dot harboe at zylin dot com>
- Cc: <java at gcc dot gnu dot org>
- Date: Wed, 26 Feb 2003 12:02:40 +0000 (GMT)
- Subject: SV: GCJ 3.3 garbage collection live-lock(conjencture) and GDB for iditos and
- References: <41D1051F31A2674C99E41CA28EE734980A1FA2@isp-ex2k.intellimade.net>
=?iso-8859-1?Q?=D8yvind=5FHarboe?= writes:
> I've found something which may be yet another clue to the live-lock problem.
>
> GDB discoveres a segmentation fault, which does not appear during normal
> execution of my program. My conjencture is that the normal Windows running
> environment is a bit more forgiving than GDB; this is intentionally
> so to make programs run in the field while making the bugs easier to find.
>
> Program received signal SIGSEGV, Segmentation fault.
> [Switching to thread 1924.0x8ac]
> 0x005cc8ed in javax.comm.SerialPortImpl.finalize() ()
> at javax/comm/SerialPortImpl.java:598
> 598 javax/comm/SerialPortImpl.java: No such file or directory.
> in javax/comm/SerialPortImpl.java
The SEGV is in javax.comm.SerialPortImpl.finalize().
Where is that code from? What is it supposed to do in your
environment? It's neither part of libgcj or Java 2.
Andrew.