Subject: Re: dlsym problem on MacOSX (code works in Linux, fails on MacOSX) comp.unix.programmer(203224)

[ Home ] Passports | National Anthems in MP3 | Live chat

Train Museum:

Warsaw, Poland • Seoul, Korea • Kyoto, Japan Forums: Rail UK, Rail Australia

Pictures:

Money • Monorail • Hong Kong light festival • High speed train • Queen Elizabeth II in Yokohama • Taro - Galapagos Tortoise

[ Home ][ Group Home ][ Random article ] [ First Article ][ Previous Article ] [ Next Article ] [ Newest Article ]

Subject: Re: dlsym problem on MacOSX (code works in Linux, fails on MacOSX)

Posted on: Tue, 27 Jul 2010 18:03:00 -0700

Kenny McCormack wrote:
> I have an app that uses dlsym() to lookup functions and then executes
> them. Usually, the function being lookedup is in the system libraries
> (i.e., libc) - i.e., it is a normal function, like read() or write(),
> etc. However, sometimes, the function being lookedup is actually in the
> app itself - i.e., we use the dlsym mechanism to invoke a "local"
> function.
>
> The former case works fine in all 3 OSs, but...
> The later case (where the function is in the app itself) works fine in
> Linux and Solaris, but fails (the dlsym() function fails with a "symbol
> not found" error) in MacOSX.
>
> Any ideas why? How to fix?
>

Not sure if it is the same issue, but I did find one time that in a MacOSX
program I was working on, a local symbol was automatically changed behind
my back. IIRC an underscore had been prepended. Before you go crazy
compile with debugging symbols on and dump the generated symbol table to be
sure it isn't the same thing.

[ Home ][ Group Home ][ Random article ] [ First Article ][ Previous Article ] [ Next Article ] [ Newest Article ]