News for hackers. Stuff that matters.

A comment on The Witchcraft Compiler Collection. Parent comment

Re:The Witchcraft Compiler Collection by zvrba on Sunday August 14, 2016 @04:25AM (#12284777)
> WCC unlinks machine code into a library, allowing you to interact with the object code and reliably include and call its functions from your own code, as if it were a shared system library rather than a black box.

Shared library is as much of a black box as an executable.

[ Parent | on HN ]
Re:The Witchcraft Compiler Collection by spacemanmatt on Sunday August 14, 2016 @12:27PM (#12286187)
Pretty sure access to internal APIs not exposed through the executable's CLI/GUI/config/etc interfaces is typically superior to no access.
[ Parent | on HN ]
Re:The Witchcraft Compiler Collection by zvrba on Monday August 15, 2016 @04:08AM (#12289241)
You're too optimistic about what it can do, here's a sample output: https://github.com/endrazine/wcc/wiki/wcch

This is not what I'd call an "API dump"; all prototypes return void pointers and allow any arguments.

Hence, it's just as much of a blackbox as the original executable is because you have no idea what the functions do, what arguments they take and what values they return.

[ Parent | on HN ]
Re:The Witchcraft Compiler Collection by spacemanmatt on Wednesday August 17, 2016 @09:01AM (#12304303)
I don't know, having the ability to compile your own test driver against it rather than manipulating the executable is what I'd be after with the tool. You may be reading too much assumption into my comment.
[ Parent | on HN ]