Make it easier to identify what undefined symbol is being called about loadlibrary HOT 5 OPEN

There isn't a good way yet, If you change the CFLAGS in the Makefile to -UNDEBUG it will dump all the undefined imports (the output is quite verbose though).

I think it will be possible to generate stubs for each undefined import that prints out the unknown symbol, but I haven't implemented that yet! I should do that. I'll need to think about it, because I think each stub will have to be generated at runtime.

Maybe I can generate a table of callsites...

from loadlibrary.

The technique that I ended up using was stepping backwards to the caller using rr and then seeing where the offset into the import table was compared to other symbols that I dumped using -UNDEBUG

from loadlibrary.

Hi, I face the same issue while porting my dll file in Linux as well. Is there any progress to identify the undefined symbol? Also, I wonder is there any workaround after locate the undefined symbol. Thank you.

from loadlibrary.

@taviso: since it seems you didn't get around to implementing the automatic stub generation yet, you should know that I already spent a considerable amount of time doing precisely that for the purposes of my android translation layer (it's more like wine than like this project, but this part is definitely applicable)

see this:
https://gitlab.com/Mis012/dalvik_standalone/-/blob/art-master/bionic_translation/linker/linker.c#L1419-L1478

it wasn't exactly easy to figure out all of the kinks, so I hope it saves you from having to deal with that yourself (though some of the kinks were aarch64 specific, not sure if this project works with aarch64 dlls)

note: I hereby dual-license that code to you under the original license AND GPLv2

from loadlibrary.

from loadlibrary.