From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 28571 invoked by alias); 12 Mar 2007 00:19:13 -0000 Received: (qmail 28390 invoked by uid 22791); 12 Mar 2007 00:19:11 -0000 X-Spam-Check-By: sourceware.org Received: from ik-out-1112.google.com (HELO ik-out-1112.google.com) (66.249.90.179) by sourceware.org (qpsmtpd/0.31) with ESMTP; Mon, 12 Mar 2007 00:19:07 +0000 Received: by ik-out-1112.google.com with SMTP id b32so1524605ika for ; Sun, 11 Mar 2007 17:19:05 -0700 (PDT) Received: by 10.70.84.6 with SMTP id h6mr9072948wxb.1173658744670; Sun, 11 Mar 2007 17:19:04 -0700 (PDT) Received: by 10.100.14.9 with HTTP; Sun, 11 Mar 2007 17:19:04 -0700 (PDT) Message-ID: <3187bd480703111719s3c32028eq450cb105637ff3b5@mail.gmail.com> Date: Mon, 12 Mar 2007 00:19:00 -0000 From: "Rich Rattanni" To: "Mark Kettenis" , jan.kratochvil@redhat.com Subject: Re: Debugging glibc crashes with GDB Cc: gdb@sourceware.org In-Reply-To: <8c7950360703111537i4f2f78ecy5bba8421b26ded34@mail.gmail.com> 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> <8c7950360703111537i4f2f78ecy5bba8421b26ded34@mail.gmail.com> 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/msg00158.txt.bz2 Jan: The debug files for glibc are installed under /lib/.debug and when I execute gdb I make sure to issue the following command, 'set debug-file-directory /lib/.debug'. On 3/11/07, shanevolpe@gmail.com wrote: > 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 >