Feature request: dynamic dll calling

[mattepiu]

My codebase (cpp) often calls separate dll functions with a precise schema:

A pointer to the function type is created.
A dll is loaded.
A Resolve function is called with the called function name i.e. Resolve("HandleMyGarbage") ant it populates the function pointer.
The function pointer is then called from now on.

dll is out of the scope/ like an API call / belonging to another project.

Is there a way this pattern can be memorized/injected in database as a node (with dll name and function name)?

[hi0001234d]

@mattepiu I am also interested in solving such problems. you said dll is out of scope so I guess you do not need runtime based pattern inclusion in database. so do you prefer any improvement in terms of edges/node pattern that can be injected or anything precise you think should be achieved?

what are the thought of @DeusData on this, @DeusData are you planning anything like runtime support but I also too prefer not making things complex by adding docker environment or is it something you prefer?

[kingchenc]

Fixed in PR #66.

Added extractDLLResolveEdges() for C/C++ files. Detects dynamic DLL resolution patterns:

• GetProcAddress(handle, "FunctionName")
• dlsym(handle, "function_name")
• .Resolve("FunctionName") / ->Resolve("FunctionName")

For each match, a CALLS edge is created from the enclosing function to a synthetic stub node representing the DLL function. Stub nodes carry dll_name and dll_function metadata. DLL name is extracted from LoadLibrary/dlopen calls in the same file (falls back to "external").

[DeusData]

Fixed in f92fd66 — ported DLL resolve tracking from PR #66. The pipeline now scans C/C++ source for GetProcAddress, dlsym, and .Resolve() patterns, creating CALLS edges to synthetic stub nodes with dll_function metadata. Thanks for the feature request!