From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 28430 invoked by alias); 20 Jul 2007 11:39:34 -0000 Received: (qmail 28264 invoked by uid 48); 20 Jul 2007 11:39:24 -0000 Date: Fri, 20 Jul 2007 11:39:00 -0000 Message-ID: <20070720113924.28263.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/msg02122.txt.bz2 ------- Comment #5 from artem at bizlink dot ru 2007-07-20 11:39 ------- > I think the best JVM-compatible action then would be > to shutdown the failed thread, > but let the other threads continue... Errrr... I wasn't really going to post this. Forgot to clear the textarea. Sorry. I don't think it's possible to detect reliably if this is a thread-local problem or not, so the best action is still to abort, but at least it will abort without consuming (2 GB?) of stack space and hard disk space (for the core). -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32836