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 11:28:00 -0000	[thread overview]
Message-ID: <20070720112759.24266.qmail@sourceware.org> (raw)
In-Reply-To: <bug-32836-7398@http.gcc.gnu.org/bugzilla/>



------- Comment #3 from artem at bizlink dot ru  2007-07-20 11:27 -------
To clarify:
this is a buffer overflow, catched by the GCJ SIGSEGV handler.
GCJ then tries to build a strack trace, but stack is obviously broken.
Still, it's not pretty that GCJ goes into an infinite loop via SIGSEGV handler,
and then into stack overflow, so I think it would be good if that infinite loop
condition can be detected somehow (for example, by traversing the intact part
of the stack trace we can easily see that we are already invoked from the
SIGSEGV handler twice or more!).


-- 


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


  parent reply	other threads:[~2007-07-20 11:28 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 ` [Bug java/32836] " artem at bizlink dot ru
2007-07-20 10:38 ` artem at bizlink dot ru
2007-07-20 11:28 ` artem at bizlink dot ru [this message]
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=20070720112759.24266.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).