From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 4718 invoked by alias); 6 Sep 2006 13:32:51 -0000 Received: (qmail 4708 invoked by uid 22791); 6 Sep 2006 13:32:49 -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 13:32:45 +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 173DF2F02A; Wed, 6 Sep 2006 16:26:59 +0200 (CEST) Received: from localhost (localhost [127.0.0.1]) by mailserver.berlin.imc-berlin.de (Postfix) with ESMTP id 4FAF0A297; Wed, 6 Sep 2006 15:32:42 +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 6C68E9BD2; Wed, 6 Sep 2006 15:32:41 +0200 (CEST) Message-ID: <44FECDF7.2050900@imc-berlin.de> Date: Wed, 06 Sep 2006 13:32:00 -0000 From: "Zarges, Olav" User-Agent: Thunderbird 1.5.0.5 (Windows/20060719) MIME-Version: 1.0 To: "gdb@sourceware.org" Cc: Daniel Jacobowitz 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> In-Reply-To: <20060821124241.GA16416@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/msg00031.txt.bz2 Daniel Jacobowitz wrote: >> >> is returned at the end of the backtrace? Eclipse just throws away the >> complete backtrace for the corresponding thread. > > What other versions of GDB are you looking at? With older versions, it was an > ^error; with newer it's a ~"console output message". I would not > expect Eclipse to throw away the backtrace if there's a console output > message. verifying again which component is responsible for "eating the backtrace" I found that those messages are created by method error(_("message....")) e.g. called from gdb/frame.c. error() finally throws an exception being caught by catch_exception(...) in function mi_execute_command(...) in gdb/mi/mi-main.c. Therefore no backtrace info is deliverd to eclipse via GDB/MI. I'm using GDB 6.5 and it looks to me that it still creates an ^error. What exactly means 'with older versions'? How can I upgrade.