Re: dlsym(...) and Intel Macs

• Subject: Re: dlsym(...) and Intel Macs
• From: Damien Sorresso <email@hidden>
• Date: Tue, 18 Jul 2006 00:18:46 -0500
• Delivered-to: email@hidden
• Delivered-to: email@hidden

On Mon, 2006-07-17 at 23:39 -0500, Damien Sorresso wrote:

On 17 Jul, 2006, at 11:33 PM, Jordan K. Hubbard wrote:

Wouldn't dlopen() be the first thing to fail if the bundle wasn't
of the appropriate architecture?   I assume Damien is also properly
checking the value of mainHandle against NULL when it's returned...

Yes, there is a NULL check in place for `dlopen(...)'. The bundle
executes just fine until it has to grab that symbol. And no, the
underscore rules have not changed as far as I know. The actual symbol
has an extra underscore added upon export, but `dlsym(...)' takes the
name of the symbol without the underscore prefix for an argument.
Besides, the symbol shows up just fine with `nm'.

In that case, dlerror() must be telling you something after the failed
dlsym() call. What does it say?

--

Damien Sorresso

Mac OS X Developer
Computer Infrastructure Support Services
Illinois State University
E-mail: email@hidden

Attachment: smime.p7s
Description: S/MIME cryptographic signature

 _______________________________________________
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

• Follow-Ups:
  • Re: dlsym(...) and Intel Macs
    • From: "Peter O'Gorman" <email@hidden>

• Prev by Date: Re: dlsym(...) and Intel Macs
• Next by Date: Re: dlsym(...) and Intel Macs
• Previous by thread: Re: dlsym(...) and Intel Macs
• Next by thread: Re: dlsym(...) and Intel Macs
• Index(es):
  • Date
  • Thread