From: Daniel Jacobowitz <drow@false.org>
To: Rene Limberger <rlimberger@mac.com>
Cc: gdb@sourceware.org
Subject: Re: implementation of backtrace on OSX?
Date: Tue, 16 Oct 2007 11:43:00 -0000 [thread overview]
Message-ID: <20071016114309.GA29578@caradoc.them.org> (raw)
In-Reply-To: <BB68D0D3-D1CD-4C06-BCDD-7A2CA2F98E73@mac.com>
On Mon, Oct 15, 2007 at 09:39:48PM -0700, Rene Limberger wrote:
> hi,
>
> can anyone give me some pointers to where in the source code the gdb backtrace
> is generated? ion linux, there is backtrace() via execinfo.h, unfortunately
> this is not available on OSX and i would like to take a peak at how gdb
> implements what we get when we type "bt". so for example:
We can't help you with GDB on OS X; Apple's got their own version.
FSF GDB doesn't support OS X.
> i am specifically interested in how gdb resolves the file and line number from
> the debug info.
It maintains a complete symbol table, so there's no small piece of
code I can point you to. The easiest way to do this is to use
binutils's addr2line utility.
--
Daniel Jacobowitz
CodeSourcery
prev parent reply other threads:[~2007-10-16 11:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-16 4:39 Rene Limberger
2007-10-16 11:43 ` Daniel Jacobowitz [this message]
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=20071016114309.GA29578@caradoc.them.org \
--to=drow@false.org \
--cc=gdb@sourceware.org \
--cc=rlimberger@mac.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).