Re: resolving backtraces created on Intel when working on PowerPC
Re: resolving backtraces created on Intel when working on PowerPC
- Subject: Re: resolving backtraces created on Intel when working on PowerPC
- From: Eric Albert <email@hidden>
- Date: Mon, 23 Jan 2006 08:59:44 -0800
On Jan 23, 2006, at 2:59 AM, j o a r wrote:
On 23 jan 2006, at 11.50, Jens Miltner wrote:
My initial attempt (after I realized that straightforward usage of
atos on the universal binary always uses the current architecture and
thus gives incorrect backtraces when the executable was run on
another architecture) was to use lipo to extract the architecture
that was run when the backtrace was produced and then use atos on the
extracted executable, e.g.
Perhaps you could file an enhancement request to give atos an "-arch"
flag!?
That'd be the right thing to do. I'm hoping to get this into the next
developer tools release, and having another bug asking for it will
help.
Any ideas how to resolve an intel backtrace on PowerPC and vice versa
(given a universal binary with symbols)?
If you can't get this to work, please file a bug report / feature
request.
I can't help with resolving an Intel backtrace on PowerPC, but for
resolving PowerPC backtraces on Intel, you can run atos with Rosetta.
As for gdb, each architecture's side of gdb is in /usr/libexec/gdb.
You can run /usr/libexec/gdb/gdb-powerpc-apple-darwin, for example, to
run a PowerPC-targeting gdb on Intel and vice versa. You can't do too
much with it beyond the Rosetta debugging case documented in the
Universal Binary Programming Guidelines, but you should be able to
resolve addresses.
Hope this helps,
Eric
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden