public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "artem at bizlink dot ru" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug java/32836] infinite loop (SIGSEGV) in java::lang::Throwable::fillInStackTrace
Date: Fri, 20 Jul 2007 10:01:00 -0000	[thread overview]
Message-ID: <20070720100058.14450.qmail@sourceware.org> (raw)
In-Reply-To: <bug-32836-7398@http.gcc.gnu.org/bugzilla/>



------- Comment #1 from artem at bizlink dot ru  2007-07-20 10:00 -------
In fact, I have two cores with this infinite loop, and they both are very
large:

$ l
total 304808
drwxr-xr-x 2 artemgr artemgr       4096 2007-07-20 11:58 ./
drwxr-xr-x 8 artemgr artemgr       4096 2007-07-20 11:57 ../
-rwxr-xr-x 1 artemgr artemgr   18949540 2007-07-20 11:25 ads*
-rw------- 1 artemgr artemgr 2317770752 2007-07-20 08:44 core.11043
-rw------- 1 artemgr artemgr 2296696832 2007-07-20 08:38 core.7490

Could be that it's some kind of an out of memory error?
Still, it is triggered only from this fillInStackTrace, otherwise the program
is working fine.


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32836


  reply	other threads:[~2007-07-20 10:01 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-20  9:53 [Bug java/32836] New: " artem at bizlink dot ru
2007-07-20 10:01 ` artem at bizlink dot ru [this message]
2007-07-20 10:38 ` [Bug java/32836] " artem at bizlink dot ru
2007-07-20 11:28 ` artem at bizlink dot ru
2007-07-20 11:34 ` artem at bizlink dot ru
2007-07-20 11:39 ` artem at bizlink dot ru
2007-07-20 14:53 ` [Bug libgcj/32836] " pinskia at gcc dot gnu dot org
2007-07-24 14:34 ` tromey at gcc dot gnu dot org

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=20070720100058.14450.qmail@sourceware.org \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@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).