Re: dlsym(...) and Intel Macs
site_archiver@lists.apple.com Delivered-To: darwin-dev@lists.apple.com On Tue, 2006-07-18 at 00:18 -0500, Damien Sorresso wrote:
On 18 Jul, 2006, at 12:14 AM, Peter O'Gorman wrote:
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?
Already checked. It returns a null string. Apparently that means nothing went wrong. Even though something has.
Okay, that's pretty strange. Since you seem to be looking up symbols in the main executable, have you tried dlsym(RTLD_DEFAULT,"Symbol"); ? If so does it give you the same (blank) error? Peter _______________________________________________ Do not post admin requests to the list. They will be ignored. Darwin-dev mailing list (Darwin-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/darwin-dev/site_archiver%40lists.appl... This email sent to site_archiver@lists.apple.com signature.asc
participants (1)
-
Peter O'Gorman