public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
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	[thread overview]
Message-ID: <20010621162603.10556.qmail@sourceware.cygnus.com> (raw)

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


             reply	other threads:[~2001-06-21  9:26 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-06-21  9:26 Tom Tromey [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-01-27 16:44 rodrigc
2001-12-18  9:40 tromey
2001-07-14  8:05 green
2001-07-09 15:56 Jianlin Chang
2001-07-02 12:06 Andrew Haley
2001-06-21  9:46 Jianlin Chang
2001-06-20 14:46 chang

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20010621162603.10556.qmail@sourceware.cygnus.com \
    --to=tromey@redhat.com \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=nobody@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).