Hi,
I'm having trouble with dll's in fasm....i used the example as a template, but when i try import my functions that are in the dll i get error in ollydbg saying it's not a valid win dll. and i export them alphabetically and everything looks rite. when i compile the example it works fine so i have no idea wat is wrong :(
any help would be appreciated :)
Thnx
Posted on 2003-01-30 11:49:32 by keyoke
try to replace the proc from the example with your own one,
and post your dll.
Posted on 2003-01-31 02:24:23 by longer
thnx longer but i rewrote the whole dll again and it works fine now but there still something strange going on when i debug the program that uses the dll ollydbg says that the entry point in the dll's pe header is wrong but still uses the exports from that dll.... i dunno if this is a problem with ollydbg or with the way fasm compiles the dll, at one stage it was saying it wasnt a valid image but still running fine.
Posted on 2003-01-31 02:45:56 by keyoke
I haven't got any such problem and I'm using OllyDbg 1.08b. Can you post some example source causing a problem here?
Posted on 2003-01-31 03:15:09 by Tomasz Grysztar
hi privalov,
i'm also using ollydbg 1.08b and using fasmw 1.45 beta2 i dont think it's a serious problem but maybe it's worth having a look at. ill post the source as soon as possible probably 2nite.
later
Posted on 2003-02-02 01:19:50 by keyoke
hey privalov here is the source that you wanted to see only GetKernelBase export is working at the moment....but u should be able to see the problem.
thnx
Posted on 2003-02-02 12:03:27 by keyoke
Oh, I see. You forgot to put the "code" and "data" flags for the ".code" and ".data" sections.
Posted on 2003-02-02 13:24:00 by Tomasz Grysztar
is there a min/max number of procs that can be implemented in a dll? because it seems to give an error when theres only 1 proc.... right now:(
Posted on 2003-02-03 13:13:06 by keyoke
AFAIK one proc is OK. there's one proc in the dll example.
Posted on 2003-02-04 00:25:49 by longer