From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 32364 invoked by alias); 6 Sep 2006 15:38:06 -0000 Received: (qmail 32356 invoked by uid 22791); 6 Sep 2006 15:38:06 -0000 X-Spam-Check-By: sourceware.org Received: from mail.imc-berlin.de (HELO mail.imc-berlin.de) (217.110.46.186) by sourceware.org (qpsmtpd/0.31) with ESMTP; Wed, 06 Sep 2006 15:38:04 +0000 Received: from mailserver.berlin.imc-berlin.de (mailserver.berlin.imc-berlin.de [10.0.0.19]) by mail.imc-berlin.de (Postfix) with ESMTP id BFAC02F026 for ; Wed, 6 Sep 2006 18:32:18 +0200 (CEST) Received: from localhost (localhost [127.0.0.1]) by mailserver.berlin.imc-berlin.de (Postfix) with ESMTP id 0438CA297 for ; Wed, 6 Sep 2006 17:38:02 +0200 (CEST) Received: from [10.0.2.29] (zarges.berlin.imc-berlin.de [10.0.2.29]) by mailserver.berlin.imc-berlin.de (Postfix) with ESMTP id 239979BD2 for ; Wed, 6 Sep 2006 17:38:01 +0200 (CEST) Message-ID: <44FEEB57.6010807@imc-berlin.de> Date: Wed, 06 Sep 2006 15:38:00 -0000 From: "Zarges, Olav" User-Agent: Thunderbird 1.5.0.5 (Windows/20060719) MIME-Version: 1.0 To: "gdb@sourceware.org" Subject: Re: gdb-6.5 produces infinite backtrace on ARM References: <44E181DE.7040905@imc-berlin.de> <20060815124053.GA18496@nevyn.them.org> <20060819052434.GA15612@nevyn.them.org> <44E999B4.5030905@imc-berlin.de> <20060821124241.GA16416@nevyn.them.org> <44FECDF7.2050900@imc-berlin.de> <20060906144356.GA2786@nevyn.them.org> <44FEE32E.60401@imc-berlin.de> <20060906151915.GA4002@nevyn.them.org> In-Reply-To: <20060906151915.GA4002@nevyn.them.org> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2006-09/txt/msg00035.txt.bz2 Daniel Jacobowitz wrote: > Oh, I see. Interesting. We'll see what we can do about this; that > does make more sense. > > However, since it has obviously listed a bunch of frames, CDT should > not be discarding the ones that did succeed! > The stack-list-frames command does not return any stack info at all if error(...) is called. Therefore CDT is not discarding anything. The is just the error message. Regards Olav