aboutsummaryrefslogtreecommitdiffstats
path: root/bfd (follow)
Commit message (Collapse)AuthorAgeFilesLines
* you can now run objects that are loaded into bruiser from a shared library ↵bloodstalker2018-01-121-3/+4
| | | | from lua. right now very simple examples work. i have to figure out how to handles runtime pointer recasts.
* load.py now loads all objects and functions along with names to c++. next is ↵bloodstalker2018-01-021-32/+72
| | | | getting them to lua.
* wipbloodstalker2017-12-312-3/+9
|
* bruiser gets the function code and name from bfd now. besides that minor ↵bloodstalker2017-12-301-4/+43
| | | | changes here and there.
* load.py recognized function entries correctly now. minor fixes and updates.bloodstalker2017-12-291-18/+112
|
* forgot the test header for obfuscator [ci skip]bloodstalker2017-12-161-1/+0
|
* obfuscator doesnt mess up var declations with init values, python driver has ↵bloodstalker2017-12-061-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
* added obfuscator, some minor changes made to load.py so it would be easier ↵bloodstalker2017-11-111-4/+5
| | | | to call python scripts from lua, general changes for a new project
* now you can run load.py from bruiser.bloodstalker2017-11-051-23/+57
|
* updatedsbloodstalker2017-10-262-5/+58
|
* now i can get the symbol names, next thing is to load the object code up in ↵bloodstalker2017-10-292-8/+117
| | | | bruiser...
* forgot this onebloodstalker2017-10-281-0/+30
|
* palying around with executbales and sosbloodstalker2017-10-283-8/+278
|
* playing around with libbfdbloodstalker2017-10-263-0/+61