Commit message (Collapse) | Author | Files | Lines | ||
---|---|---|---|---|---|
2018-01-12 | you can now run objects that are loaded into bruiser from a shared library ↵ | bloodstalker | 1 | -3/+4 | |
from lua. right now very simple examples work. i have to figure out how to handles runtime pointer recasts. | |||||
2018-01-02 | load.py now loads all objects and functions along with names to c++. next is ↵ | bloodstalker | 1 | -32/+72 | |
getting them to lua. | |||||
2017-12-31 | wip | bloodstalker | 2 | -3/+9 | |
2017-12-30 | bruiser gets the function code and name from bfd now. besides that minor ↵ | bloodstalker | 1 | -4/+43 | |
changes here and there. | |||||
2017-12-29 | load.py recognized function entries correctly now. minor fixes and updates. | bloodstalker | 1 | -18/+112 | |
2017-12-16 | forgot the test header for obfuscator [ci skip] | bloodstalker | 1 | -1/+0 | |
2017-12-06 | obfuscator doesnt mess up var declations with init values, python driver has ↵ | bloodstalker | 1 | -116/+216 | |
been updated, not finished yet, bruiser now gets the objects from load.py, executioner will handle running the objects and registering them with lua | |||||
2017-11-11 | added obfuscator, some minor changes made to load.py so it would be easier ↵ | bloodstalker | 1 | -4/+5 | |
to call python scripts from lua, general changes for a new project | |||||
2017-11-05 | now you can run load.py from bruiser. | bloodstalker | 1 | -23/+57 | |
2017-10-26 | updateds | bloodstalker | 2 | -5/+58 | |
2017-10-29 | now i can get the symbol names, next thing is to load the object code up in ↵ | bloodstalker | 2 | -8/+117 | |
bruiser... | |||||
2017-10-28 | forgot this one | bloodstalker | 1 | -0/+30 | |
2017-10-28 | palying around with executbales and sos | bloodstalker | 3 | -8/+278 | |
2017-10-26 | playing around with libbfd | bloodstalker | 3 | -0/+61 | |