From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 5007 invoked by alias); 21 Feb 2006 04:33:04 -0000 Received: (qmail 4999 invoked by uid 22791); 21 Feb 2006 04:33:04 -0000 X-Spam-Check-By: sourceware.org Received: from gandalf.inter.net.il (HELO gandalf.inter.net.il) (192.114.186.17) by sourceware.org (qpsmtpd/0.31) with ESMTP; Tue, 21 Feb 2006 04:33:03 +0000 Received: from nitzan.inter.net.il (nitzan.inter.net.il [192.114.186.20]) by gandalf.inter.net.il (MOS 3.7.1-GA) with ESMTP id HYB28364; Tue, 21 Feb 2006 06:32:56 +0200 (IST) Received: from HOME-C4E4A596F7 (IGLD-80-230-143-189.inter.net.il [80.230.143.189]) by nitzan.inter.net.il (MOS 3.7.3-GA) with ESMTP id CTE95704 (AUTH halo1); Tue, 21 Feb 2006 06:32:55 +0200 (IST) Date: Tue, 21 Feb 2006 10:01:00 -0000 Message-Id: From: Eli Zaretskii To: Shaun Jackman , gdb-patches@sourceware.org In-reply-to: <20060220220331.GA29363@nevyn.them.org> (message from Daniel Jacobowitz on Mon, 20 Feb 2006 17:03:31 -0500) Subject: Re: Fix a crash when stepping and unwinding fails Reply-to: Eli Zaretskii References: <20060220220331.GA29363@nevyn.them.org> X-IsSubscribed: yes Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org X-SW-Source: 2006-02/txt/msg00389.txt.bz2 > Date: Mon, 20 Feb 2006 17:03:31 -0500 > From: Daniel Jacobowitz > > Now we'll issue this error instead, and stop stepping: > > Could not step out of the function at 0x80144400 - unwinding failed > [...] > Hmm. Alternatively, we could stop stepping without an error. Would > that be better? Seems likely. I'll wait for comments before I try > implementing that, though. Should we warn when we do that, in addition > to stopping, or is the warning just noise? How about making it a warning that depends on "set verbose"? Btw, I think we should document this message in the manual anyway.