From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 13399 invoked by alias); 19 Jul 2009 16:03:55 -0000 Received: (qmail 13230 invoked by uid 22791); 19 Jul 2009 16:03:54 -0000 X-SWARE-Spam-Status: No, hits=-1.0 required=5.0 tests=BAYES_50,RCVD_IN_DNSWL_LOW X-Spam-Check-By: sourceware.org Received: from lon1-post-1.mail.demon.net (HELO lon1-post-1.mail.demon.net) (195.173.77.148) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Sun, 19 Jul 2009 16:03:47 +0000 Received: from arrows.demon.co.uk ([83.105.72.193] helo=Catherine) by lon1-post-1.mail.demon.net with smtp (Exim 4.69) id 1MSYrZ-0005jH-Wy for gdb@sourceware.org; Sun, 19 Jul 2009 16:03:45 +0000 Message-ID: <8889C7D9C664436F8F547CB15F53C01C@Catherine> From: "Catherine Smith" To: Subject: Backtracing broken core dumps Date: Sun, 19 Jul 2009 16:03:00 -0000 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=original Content-Transfer-Encoding: 7bit Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2009-07/txt/msg00128.txt.bz2 I have attempted to find back traces of several core dumps which have resulted from executing damaged pointers to functions, or null pointers to functions. Sometimes a gdb command of the form set pc=$lr would help, except that gdb says (gdb) set pc=$lr You can't do that without a process to debug I have to resort to careful editting of the core file with a binary editor. This works, is useful, but isn't very friendly. Similarly today I had a crash in an Arm assembler memcpy() . Careful unwinding the stack by hand and editting the core dump allowed a stack trace to be extracted. Is there a gdb command which allows this sort of change? If not, could one be created? Thanks, John Smith