1. dll.e question
- Posted by Hayden McKay <hmck1 at dodo.com?au> Jul 01, 2007
- 660 views
I think I've seen a similar post for this before. I could probably do some testing to figure this out but heres may question anyway... I want to use KERNEL32.DLL-GetProcAddress() to get the address of a c routine, I have some embedded asm code that uses c funcs and i want to link it staticly, ie: the returned addresses will either be from a *.dll or a *.so file... anyway i want to know if I can pass dll.e's open_dll() return value to GetProcAddress() or do I have to use GetModuleHandle() or LoadLibrary() to aquire the correct handle?
2. Re: dll.e question
- Posted by CChris <christian.cuvier at ag?iculture.gouv.fr> Jul 01, 2007
- 633 views
Hayden McKay wrote: > > I think I've seen a similar post for this before. I could probably do some > testing > to figure this out but heres may question anyway... > > I want to use KERNEL32.DLL-GetProcAddress() to get the address of a c routine, > I have some embedded asm code that uses c funcs and i want to link it > staticly, > ie: the returned addresses will either be from a *.dll or a *.so file... > anyway > i want to know if I can pass dll.e's open_dll() return value to > GetProcAddress() > or do I have to use GetModuleHandle() or LoadLibrary() to aquire the correct > handle? The entry point that open_dll() returns is good for Windows, as shown in the dsearch.exw demo program. Hopefully the same holds under Linux for .so files. CChris
3. Re: dll.e question
- Posted by Matt Lewis <matthewwalkerlewis at g?ail.com> Jul 02, 2007
- 645 views
Hayden McKay wrote: > > I think I've seen a similar post for this before. I could probably do some > testing > to figure this out but heres may question anyway... > > I want to use KERNEL32.DLL-GetProcAddress() to get the address of a c routine, > I have some embedded asm code that uses c funcs and i want to link it > staticly, > ie: the returned addresses will either be from a *.dll or a *.so file... > anyway > i want to know if I can pass dll.e's open_dll() return value to > GetProcAddress() > or do I have to use GetModuleHandle() or LoadLibrary() to aquire the correct > handle? An easier way is to use define_c_var. It simply returns the address of the symbol. While made for using variables, it works for routines, as well. Matt
4. Re: dll.e question
- Posted by Hayden McKay <hmck1 at dodo.co?.au> Jul 04, 2007
- 648 views
thanks matt, nice reply! define_c_var is sometin' most people would overlook on this subject. must thankyou for good post...