From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 9826 invoked by alias); 11 Mar 2007 22:37:16 -0000 Received: (qmail 9816 invoked by uid 22791); 11 Mar 2007 22:37:16 -0000 X-Spam-Check-By: sourceware.org Received: from an-out-0708.google.com (HELO an-out-0708.google.com) (209.85.132.244) by sourceware.org (qpsmtpd/0.31) with ESMTP; Sun, 11 Mar 2007 22:37:12 +0000 Received: by an-out-0708.google.com with SMTP id c2so1081116anc for ; Sun, 11 Mar 2007 15:37:10 -0700 (PDT) Received: by 10.114.113.1 with SMTP id l1mr1020662wac.1173652629890; Sun, 11 Mar 2007 15:37:09 -0700 (PDT) Received: by 10.115.107.7 with HTTP; Sun, 11 Mar 2007 15:37:09 -0700 (PDT) Message-ID: <8c7950360703111537i4f2f78ecy5bba8421b26ded34@mail.gmail.com> Date: Sun, 11 Mar 2007 22:37:00 -0000 From: shanevolpe@gmail.com To: "Mark Kettenis" Subject: Re: Debugging glibc crashes with GDB Cc: rattanni@gmail.com, gdb@sourceware.org In-Reply-To: <200703112136.l2BLaTRx006665@brahms.sibelius.xs4all.nl> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <3187bd480703111104r46b15863g2d59714f5cc3793e@mail.gmail.com> <200703112136.l2BLaTRx006665@brahms.sibelius.xs4all.nl> X-IsSubscribed: yes 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: 2007-03/txt/msg00157.txt.bz2 Mark, gdb version: 6.6 glibc version: 2.5 ARCH: PXA270 (xscale) Linux Version: 2.6.20 (Distro: OpenEmbedded) Regards, Shane (Co-employee with Rich) On 3/11/07, Mark Kettenis wrote: > > Date: Sun, 11 Mar 2007 14:04:41 -0400 > > From: "Rich Rattanni" > > > > Below you will find the GDB output related to my question. My problem > > is that when I try to debug a program after receiving a glibc abort > > error (MALLOC_CHECK = 2) I cannot backtrace the program to find out > > what piece of my application caused the problem. I can see the call > > to raise and abort, but then I get the error message "Backtrace > > stopped: > > frame did not save the PC". Could this be due to code compiled with > > the -fomit-frame-pointers options. I am really pulling my hair out > > over this one, any guidance or suggests would be vastly appreciated. > > If further forensic info is required just ask. Thanks in advance. > > Note: I can switch the thread I am in and view other stack backtraces > > with no problem. > > We need more information to help you. What version of gdb are you > using? On what machine architecture? What version of glibc is this? > What flavour of Linux are you using? > -- Registered Linux User: #293401