From: Eric Christopher <echristo@apple.com>
To: Ethan Tira-Thompson <ejt@andrew.cmu.edu>
Cc: binutils@sourceware.org
Subject: Re: libbfd Mac OS X support?
Date: Mon, 01 May 2006 00:29:00 -0000 [thread overview]
Message-ID: <72556FFC-37B0-4DB3-8C35-B10A92C9F38F@apple.com> (raw)
In-Reply-To: <2119EFE1-B864-43C7-9847-279395E88148@andrew.cmu.edu>
> ??:0
> However, I see GDB is somehow able to extract file/function info,
> and afaik, it's using libbfd...
>
> 1. Which copy of bfd should I be linking against (i.e. the one in
> gcc, or gdb, or binutils...?)
There's a copy of bfd in the Apple version of gdb that has some
functionality, but...
> 2. Is bfd_find_nearest_line simply unimplemented on OS X, or is
> there something deeper?
Something deeper. Mostly bfd is unsupported for OS X unfortunately.
> 3. Do you know how GDB extracts line info? (i.e. suggestions for
> workaround/next step?)
I'd suggest using the bfd work for OS X available from the Apple
version of gdb.
-eric
prev parent reply other threads:[~2006-05-01 0:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-01 0:11 Ethan Tira-Thompson
2006-05-01 0:29 ` Eric Christopher [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=72556FFC-37B0-4DB3-8C35-B10A92C9F38F@apple.com \
--to=echristo@apple.com \
--cc=binutils@sourceware.org \
--cc=ejt@andrew.cmu.edu \
/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).