From mboxrd@z Thu Jan  1 00:00:00 1970
From: Tom Tromey <tromey@redhat.com>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org
Subject: Re: java/3307: compiled program core dump in GC_find_limit
Date: Thu, 21 Jun 2001 09:26:00 -0000
Message-id: <20010621162603.10556.qmail@sourceware.cygnus.com>
X-SW-Source: 2001-06/msg00903.html
List-Id: <gcc-prs.sourceware.org>

The following reply was made to PR java/3307; it has been noted by GNATS.

From: Tom Tromey <tromey@redhat.com>
To: chang@platform.com
Cc: gcc-gnats@gcc.gnu.org
Subject: Re: java/3307: compiled program core dump in GC_find_limit
Date: 21 Jun 2001 09:32:46 -0600

 >> Compiled program core dump, stack trace is:
 >> #0  0xff314130 in GC_find_limit (p=0xffbeea5c "", up=1)
 >>     at ../../../gcc-3.0/boehm-gc/os_dep.c:644
 
 This isn't the location of the actual segv.
 Instead this is an implementation artifact of the GC.
 Please read:
 
     http://gcc.gnu.org/java/faq.html#5_2
 
 ... then reproduce the problem and send us the real backtrace.
 
 Please *don't* send the core file.  It is useless to me.
 
 Thanks,
 Tom