From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 31214 invoked by alias); 16 Oct 2003 00:07:15 -0000 Mailing-List: contact gdb-patches-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sources.redhat.com Received: (qmail 31206 invoked from network); 16 Oct 2003 00:07:14 -0000 Received: from unknown (HELO mx1.redhat.com) (66.187.233.31) by sources.redhat.com with SMTP; 16 Oct 2003 00:07:14 -0000 Received: from int-mx1.corp.redhat.com (int-mx1.corp.redhat.com [172.16.52.254]) by mx1.redhat.com (8.11.6/8.11.6) with ESMTP id h9G07EM16869 for ; Wed, 15 Oct 2003 20:07:14 -0400 Received: from pobox.corp.redhat.com (pobox.corp.redhat.com [172.16.52.156]) by int-mx1.corp.redhat.com (8.11.6/8.11.6) with ESMTP id h9G07Er01791; Wed, 15 Oct 2003 20:07:14 -0400 Received: from localhost.localdomain (vpn50-39.rdu.redhat.com [172.16.50.39]) by pobox.corp.redhat.com (8.12.8/8.12.8) with ESMTP id h9G07DwC017328; Wed, 15 Oct 2003 20:07:13 -0400 Received: (from kev@localhost) by localhost.localdomain (8.11.6/8.11.6) id h9G077C23791; Wed, 15 Oct 2003 17:07:07 -0700 Date: Thu, 16 Oct 2003 00:07:00 -0000 From: Kevin Buettner Message-Id: <1031016000707.ZM23790@localhost.localdomain> In-Reply-To: Andrew Cagney "Re: [PATCH] frv-tdep.c: Stop backtraces in entry func, not entry file" (Oct 14, 5:55pm) References: <1031014205135.ZM29586@localhost.localdomain> <3F8C70CE.5020504@gnu.org> To: Andrew Cagney Subject: Re: [PATCH] frv-tdep.c: Stop backtraces in entry func, not entry file Cc: gdb-patches@sources.redhat.com MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-SW-Source: 2003-10/txt/msg00528.txt.bz2 On Oct 14, 5:55pm, Andrew Cagney wrote: > > An FR-V user reported being unable to see useful backtraces when > > debugging functions inside the entry file. This patch fixes that > > problem. I think there's a problem with inside_entry_func() itself, > > but that's a separate issue. (If you are in the entry file, > > backtraces don't stop at the entry func - they attempt to continue > > beyond, but they do stop shortly thereafter.) > > What happens if that test is removed? At the moment, the behavior is the same whether the test is there or not. That is, things work as expected so long as your're in main() or above. If you go below main(), then things break down. The inside_entry_func() test ought to stop backtraces from going too far, but for FR-V at least, it seems to be broken. Here's an example of where things break down: 0x00010118 in _start () 1: x/i $pc 0x10118 <_start+280>: call 0x11dc0 (gdb) bt #0 0x00010118 in _start () #1 0x00018ed4 in _write_r (ptr=0x0, fd=0, buf=0x0, cnt=5) at /ocotillo2/devo-frv/frv-elf/bld/../../devo/newlib/libc/reent/writer.c:58 Previous frame inner to this frame (corrupt stack?) Kevin