Displaying 4 results from an estimated 4 matches for "symbol_not_found".
2007 Jul 20
2
[LLVMdev] Trouble Resolving Objective-C Symbols in lli
...s like libtool's
static lt_ptr
sys_dl_sym (loader_data, module, symbol)
lt_user_data loader_data;
lt_module module;
const char *symbol;
{
lt_ptr address = dlsym (module, symbol);
if (!address)
{
LT_DLMUTEX_SETERROR (DLERROR (SYMBOL_NOT_FOUND));
}
return address;
}
break the ability to detect an undefined symbol versus a symbol with a
value of 0 because it sets the lt_dlerror() whenever dlsym() returns 0.
Perhaps a bug in libtool, I was looking at 1.5.6, but it's a twisty
maze and I could have taken a wrong turn....
2007 Jul 20
0
[LLVMdev] Trouble Resolving Objective-C Symbols in lli
...ys_dl_sym (loader_data, module, symbol)
> lt_user_data loader_data;
> lt_module module;
> const char *symbol;
> {
> lt_ptr address = dlsym (module, symbol);
>
> if (!address)
> {
> LT_DLMUTEX_SETERROR (DLERROR (SYMBOL_NOT_FOUND));
> }
>
> return address;
> }
>
> break the ability to detect an undefined symbol versus a symbol with a
> value of 0 because it sets the lt_dlerror() whenever dlsym() returns 0.
> Perhaps a bug in libtool, I was looking at 1.5.6, but it's a twisty
&...
2007 Jul 20
0
[LLVMdev] Trouble Resolving Objective-C Symbols in lli
Hi Ralph,
On Fri, 2007-07-20 at 10:38 +0100, Ralph Corderoy wrote:
> Hi Chris,
> I could be missing something, but shouldn't the use of dlsym() be
>
> char *err;
> void *p;
>
> if ((err = dlerror())) {
> error("earlier undetected dlerror: %s\n", err);
> }
> p = dlsym(handle, sym);
> if ((err = dlerror())) {
>
2007 Jul 20
4
[LLVMdev] Trouble Resolving Objective-C Symbols in lli
Hi Chris,
> Once you have that, you are hitting another problem. Specifically,
> the JIT::getPointerToNamedFunction method in
> lib/ExecutionEngine/JIT/Intercept.cpp just does a dlsym on missing
> symbols. If dlsym returns null, you get the error message.
>
> The problem here is that .objc_class_name_* are special symbols that
> are used by the objc linker support and they