Jordan Francis Moran-Meyers

a possible way todo this would be to store a kind of template debug section for both x86 and x64 targets and configure it as necessary on the fly before...

``` typedef struct _IMAGE_DEBUG_DIRECTORY { DWORD Characteristics; DWORD TimeDateStamp; WORD MajorVersion; WORD MinorVersion; DWORD Type; DWORD SizeOfData; DWORD AddressOfRawData; DWORD PointerToRawData; } IMAGE_DEBUG_DIRECTORY, *PIMAGE_DEBUG_DIRECTORY; ``` this seems to be the...

Is it possible the type info could also be structs and the like?

if you want to use it in a simple terminal application you probably want to setup something like this: ``` using System; using System.Text; using System.Threading; using System.Threading.Tasks; using VtNetCore.VirtualTerminal;...

``` pub fn get_entities(&self, kind: EntityKind) -> Vec { self.0 .get_entity() .get_children() .into_iter() .filter(|e| e.get_kind() == kind) .filter(|e| !e.is_in_system_header()) .collect::() } ``` im not sure this traverses the whole tree...

in terms of c++ issues I am testing this tool agenst this https://github.com/jfmherokiller/CommonLibSSE/tree/ClangFixes (its a modified version of commonlibsse that is more compatable with clang. The reason i said it...

> > > > im not sure this traverses the whole tree eg I think it only goes to the next level > > Yeah that is accurate. I didn't...