From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 7022 invoked by alias); 25 Apr 2005 20:44:54 -0000 Mailing-List: contact gdb-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sources.redhat.com Received: (qmail 6987 invoked from network); 25 Apr 2005 20:44:49 -0000 Received: from unknown (HELO nevyn.them.org) (66.93.172.17) by sourceware.org with SMTP; 25 Apr 2005 20:44:49 -0000 Received: from drow by nevyn.them.org with local (Exim 4.50 #1 (Debian)) id 1DQARk-0006sf-9M; Mon, 25 Apr 2005 16:44:48 -0400 Date: Mon, 25 Apr 2005 20:51:00 -0000 From: Daniel Jacobowitz To: Jon Ringle Cc: gdb@sources.redhat.com Subject: Re: Writing regs to corefile Message-ID: <20050425204447.GA26391@nevyn.them.org> Mail-Followup-To: Jon Ringle , gdb@sources.redhat.com References: <200504251636.13657.jon.ringle@comdial.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200504251636.13657.jon.ringle@comdial.com> User-Agent: Mutt/1.5.8i X-SW-Source: 2005-04/txt/msg00183.txt.bz2 On Mon, Apr 25, 2005 at 04:36:13PM -0400, Jon Ringle wrote: > (gdb) bt > #0 0x401672d8 in _IO_vfprintf (s=0x1d, format=0x20c3afc "\n*** PID %d returning from signal %d @ pc %08x lr %08x\n", ap=Cannot access memory at address 0xbee01f44 > ) at vfprintf.c:209 > #1 0x40175d5c in _IO_vsprintf (string=0x20f7aa8 "\n*** PID 79 returning from signal 13 @ pc 401b9304 lr 401039d8\n", > format=0x20c3afc "\n*** PID %d returning from signal %d @ pc %08x lr %08x\n", args=0xbee0252c) at iovsprintf.c:47 > #2 0x020ba51c in dbgPrintf (fmt=0x20c3afc "\n*** PID %d returning from signal %d @ pc %08x lr %08x\n") at dbgprint.c:184 > #3 0x0200b278 in client_sigaction (sig=13, psi=0xbee02624, arg=0xbee026a4) at signals.c:103 > #4 0x40101fc8 in pthread_sighandler_rt (signo=13, si=0xbee02624, uc=0xbee026a4) at signals.c:119 > #5 > Previous frame inner to this frame (corrupt stack?) Well, that's not supposed to happen. You want to figure out why it did... > I can't seem to write directly to the core file register set from within gdb > (which is why I was hand editing the core file): > (gdb) set $r0 = 0xffffffe4 > You can't do that without a process to debug. Yeah. This is a bit unfortunate. Maybe we should allow the loaded copy of the registers to be changed. -- Daniel Jacobowitz CodeSourcery, LLC