From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 24421 invoked by alias); 20 Jul 2007 11:28:10 -0000 Received: (qmail 24267 invoked by uid 48); 20 Jul 2007 11:27:59 -0000 Date: Fri, 20 Jul 2007 11:28:00 -0000 Message-ID: <20070720112759.24266.qmail@sourceware.org> X-Bugzilla-Reason: CC References: Subject: [Bug java/32836] infinite loop (SIGSEGV) in java::lang::Throwable::fillInStackTrace In-Reply-To: Reply-To: gcc-bugzilla@gcc.gnu.org To: gcc-bugs@gcc.gnu.org From: "artem at bizlink dot ru" Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org X-SW-Source: 2007-07/txt/msg02120.txt.bz2 ------- 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