Programmatic backtrace in userspace application...

• Subject: Programmatic backtrace in userspace application...
• From: Shawn Erickson <email@hidden>
• Date: Wed, 14 Dec 2005 08:50:38 -0800
• Delivered-to: email@hidden
• Delivered-to: email@hidden
• Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=VtAQrbqzw1YP7ILVg6ATbfrCtiWHhgifv0iKYJurReWoep7A0FX0JsM0+/I+7pu7DVuHmnBGq620Ew5yQ/RWhwjqxeug8u9H67EYXwL6jP/ajgXC3i079dxfhA8olq0BnS/uSEPe50jdfXxNWCwYcFMGUcT4CRRpv9QIOylZKys=

I am looking for a simple way to log a backtrace to help me understand
runtime callers of some code that I may have to modify (based on who
is calling it, etc.). I found the following source code example but
before I spend time pulling it apart and putting it back together so I
can use it in my situation... I have a couple of questions.

<http://developer.apple.com/samplecode/MoreIsBetter/listing41.html>

1) Does the system (10.4 and later) provide a backtrace logging
facility for MACHO binaries that can be called during runtime in an
arbitrary thread? (without faulting the application)

2) If not then is the MoreBacktrace.c code still correct enough for
PowerPC based systems using 10.4 and ok to use with gcc 3.3 / 4.0 C++
compiled code?

-Shawn
 _______________________________________________
Do not post admin requests to the list. They will be ignored.
Darwin-dev mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/darwin-dev/email@hidden

This email sent to email@hidden

• Prev by Date: Re: smartcard info
• Next by Date: Re: smartcard info
• Previous by thread: Re: smartcard info
• Next by thread: Libtool (ld) problem in makefile. Is the GCC 4.0 distribution broken?
• Index(es):
  • Date
  • Thread