Home > Back-end >  A known OCX library calls a dynamic library, how to get to this OCX library calls dynamic libraries
A known OCX library calls a dynamic library, how to get to this OCX library calls dynamic libraries

Time:10-05

Urgent ask ace:
A known OCX library calls a dynamic library, how to get to this OCX library calls dynamic libraries which interface? (no ocx code)

CodePudding user response:

Analysis of PE format, check the import table of PE
The Luo Yunbin win32 compilation book in the tutorial

CodePudding user response:

Can you give us detailed said?

CodePudding user response:

PE (" portable executable, "portable executable file) file format, is WindwosNT, Microsoft Windows95 and Win32 subset of executable binary file format; In WindowsNT, driver is this format, it can also be applied to various kinds of target files and library files,

This file format is designed by Microsoft, and in 1993 by TIS (tool interface standard, tools) interface standard committee (by Microsoft, Intel, Borland, Watcom, IBM, etc.) is approved, it obviously based on the many knowledge COFF file format, COFF (" common object file fromat ", common object file format) is applied to several kind of UNIX system (3) and object files in the VMS (4) system and the executable file format,

Ok, above is copy of http://bbs.pediy.com/showthread.php? Threadid=21932

PE format has import table export table, there are many other things, the import table from other links in the function of IMAGE_DIRECTORY_ENTRY_EXPORT part (PE), the export table is a function of provide for the use of other programs, and exports of a DLL in the Delphi part in the export list IMAGE_DIRECTORY_ENTRY_IMPORT part (PE), see the link above, or baidu PE file format

CodePudding user response:

If it is static load DLLS can through the PE file format in the input table to know what call the interface,
If it is dynamic load DLLS need through the debugger to debug to know what call the interface,

CodePudding user response:

reference 4 floor aqtata response:
if it is a static load the DLL, you can through the PE file format in the input table call what interface,
If it is dynamic load DLLS need through the debugger to debug to know what interface, call


Dynamic can hook Loadlibrary, this in the Windows core programming has

Can also write a DLL export functions and ocx call as dynamic libraries, do not need to realize the function, ocx call dynamic libraries call DLL you wrote first, then your DLL call the actual dynamic library, all function run once, you will know that call what, the most simple, but the premise is you need to know what the import function of dynamic link library,
  • Related