Artur K.
Artur K.
There is also this project here https://github.com/GameTechDev/MaskedOcclusionCulling might be of some use
Exactly so. AFAIK there is no identification information contained inside lib/tpl files.
Yup, the format of signature files could be made a bit more robust: ``` json { "Vendor": "Borland", "CompilerName" : "TurboC 3.0", "Language": "C", "Version": "3.0", "SignatureBlocks": [{ "Model": "Large",...
Common signature format: agreed - will try to flesh it out and post it here.
John, should we consider other pattern schemes ? Once upon a time I've had some fun with an xbox emulator that used pattern matching to identify SDK functions, and rewritten...
As for YARA, I think their pattern matching language is not a very good match for our purposes ? What we might consider is pattern disambiguation by symbol names ?...
@lab313ru I don't believe we can use any of their tooling in our open source projects though ?
Started writing the spec for the pattern files: https://github.com/nemerle/dcc/wiki/Cross-decompiler-signature-specification
Well, the list of functions has to be built beforehand and dumping the names of all functions from DccProject object can work. Te script will need to be written though
It looks like the 'main' entry-point pattern locator is at fault here, will look into it as time allows