|
-
June 9th, 2004, 06:22 AM
#16
Re: Re: Re: Re: re:
Originally posted by Andreas Masur
Then check whether the function is exported through the lib file...using the dependency walker for example...
Hi Andreas,
How to do it???
Do you mean to open the .lib file in the dependency walker??
I think we cannot open a .lib file in the dependency walker.
If you mean to open the .dll file in the dependency walker, then the function is found when the dll is opened in the dependency walker and the other dependent dlls are also available.
Am i correct or am I missing something?
With Thanks,
A.Ilamparithi.
-
June 9th, 2004, 07:54 AM
#17
Re: Re: Re: Re: Re: re:
Originally posted by ilamparithi
Do you mean to open the .lib file in the dependency walker??
If you mean to open the .dll file in the dependency walker, then the function is found when the dll is opened in the dependency walker and the other dependent dlls are also available.
Well...yes, my previous answer was some kind of short...what I meant was actually both...however, for the import library you would rather use 'dumpbin /exports library'...
-
June 9th, 2004, 08:21 AM
#18
Re: Re: Re: Re: Re: Re: re:
Originally posted by Andreas Masur
Well...yes, my previous answer was some kind of short...what I meant was actually both...however, for the import library you would rather use 'dumpbin /exports library'...
Hi Andreas,
When i used dumpbin, i got info like this
File Type: LIBRARY
Exports
ordinal name
_IcmpCloseHandle@4
_IcmpCreateFile@0
_IcmpParseReplies@8
_IcmpSendEcho2@44
_IcmpSendEcho@32
_do_echo_rep@40
_do_echo_req@40
_register_icmp@0
Summary
A5 .debug$S
14 .idata$2
14 .idata$3
4 .idata$4
4 .idata$5
A .idata$6
IcmpParseReplies seems to be there.
Is there is any solution for this??
With Thanks,
A.Ilamparithi.
-
June 9th, 2004, 09:14 AM
#19
Well...this is somehow strange...however, the dependency of the windows header files is controlled by many 'ifdefs' guards...so, one thing that comes to my mind is, that the inclusion of some header leads to a define which prevents the 'icmpapi' header file...
However, I haven't dealt with that stuff before...
-
June 9th, 2004, 09:34 AM
#20
the prototype in the header is incorrect...
Code:
DWORD
IcmpParseReplies(
LPVOID ReplyBuffer,
DWORD ReplySize
);
needs to be __stdcall
Code:
DWORD WINAPI
IcmpParseReplies(
LPVOID ReplyBuffer,
DWORD ReplySize
);
either change the icmpapi.h or define the prototypes yourself <with EXTERN_C or extern "C">
Last edited by Mick; June 9th, 2004 at 09:38 AM.
-
June 9th, 2004, 10:49 PM
#21
Great!
Originally posted by Mick
the prototype in the header is incorrect...
Code:
DWORD
IcmpParseReplies(
LPVOID ReplyBuffer,
DWORD ReplySize
);
needs to be __stdcall
Code:
DWORD WINAPI
IcmpParseReplies(
LPVOID ReplyBuffer,
DWORD ReplySize
);
either change the icmpapi.h or define the prototypes yourself <with EXTERN_C or extern "C">
Hi Mick,
Great Mick!
It works!
Thanks a lot!
Thank you Andreas and Usman for your help!
With Thanks,
A.Ilamparithi.
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
|
Click Here to Expand Forum to Full Width
|