From: Mark Kettenis <mark.kettenis@xs4all.nl>
To: rattanni@gmail.com
Cc: gdb@sourceware.org
Subject: Re: Debugging glibc crashes with GDB
Date: Sun, 11 Mar 2007 21:36:00 -0000 [thread overview]
Message-ID: <200703112136.l2BLaTRx006665@brahms.sibelius.xs4all.nl> (raw)
In-Reply-To: <3187bd480703111104r46b15863g2d59714f5cc3793e@mail.gmail.com> (rattanni@gmail.com)
> Date: Sun, 11 Mar 2007 14:04:41 -0400
> From: "Rich Rattanni" <rattanni@gmail.com>
>
> 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?
next prev parent reply other threads:[~2007-03-11 21:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-11 18:04 Rich Rattanni
2007-03-11 21:36 ` Mark Kettenis [this message]
2007-03-11 22:37 ` shanevolpe
2007-03-12 0:19 ` Rich Rattanni
2007-03-12 1:15 ` Daniel Jacobowitz
2007-03-12 8:32 ` Mark Kettenis
2007-03-12 11:04 ` Daniel Jacobowitz
2007-03-12 23:59 ` Michael Snyder
2007-03-13 15:51 ` Daniel Jacobowitz
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200703112136.l2BLaTRx006665@brahms.sibelius.xs4all.nl \
--to=mark.kettenis@xs4all.nl \
--cc=gdb@sourceware.org \
--cc=rattanni@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox