Re: dyld sources vs dyld binaries

• Subject: Re: dyld sources vs dyld binaries
• From: Eric Albert <email@hidden>
• Date: Fri, 16 Jun 2006 15:20:20 -0700
• Delivered-to: email@hidden
• Delivered-to: email@hidden

On Jun 16, 2006, at 3:06 PM, Cedric Luthi wrote:

Here is an excerpt of a backtrace on a call to NSCreateObjectFileImageFromMemory (ran on Mac OS X 10.4.6 ppc)
You can clearly identify that compatibilityChecks is called inside the ImageLoaderMachO constructor.

1 dyld 0x8fe1168c ImageLoaderMachO::compatibilityChecks(ImageLoader::LinkContext const&) + 316
2 dyld 0x8fe12ddc ImageLoaderMachO::ImageLoaderMachO [in-charge](char const*, mach_header const*, unsigned long long, ImageLoader::LinkContext const&) + 224
3 dyld 0x8fe05af4 dyld::loadFromMemory(unsigned char const*, unsigned long long, char const*) + 996
4 dyld 0x8fe0860c NSCreateObjectFileImageFromMemory + 120
5 libSystem.B.dylib 0x9017dca0 NSCreateObjectFileImageFromMemory + 104

Thanks,
Eric

_______________________________________________
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

• Prev by Date: dyld sources vs dyld binaries
• Next by Date: Re: Apple Libtool
• Previous by thread: dyld sources vs dyld binaries
• Next by thread: popen with r+
• Index(es):
  • Date
  • Thread