jbremer / ssexy Goto Github PK

Ability to Single-Step Debug a sequence of instructions, to see what's going wrong and/or if it's working correctly.
This will take a series of lines of assembly or machine code and modify these in such a way that it will while(1); between each instruction, from there do some windows hackery in order to obtain the xmm registers etc, in the trace it should show the instruction, in disassembled format, and the registers that were changed, after it. The initial registers should be shown as well, or included as lines/machine code.
When referenced, m128s should be displayed as well.

Improvements on test cases and new test cases etc.

A new Test Case mini-framework should be made which allows instructions that handle operations on memory.

Every instruction that is used by common applications, should be implemented, this will be done here.

Read and Write to and from 8, 16, or 32 bit general purpose registers, memory addresses, etc..
Each of these read and writes have to be tested carefully, because they will (initially) be the core of the sseify framework.

In order to convert existing software into SSEified executables we are going to need a PE parsing library, and more importantly, a PE creation library. PE creation libraries do not really exist, so this will be written from scratch, and while we are at it, implement the parsing from scratch as well.

I am developer for the ArchAssault project, we would like to release this in our distro but I noticed its missing a license. Can you please add a license file to it?

Many instructions in the general purpose instructions set flags depending on the calculation being performed.
A tracer should be made which tells us which instruction sets a certain flag which is being used in a conditional jump (and instruction alike).
Helper functions should be made which handle certain flags and the tests related to it, so conditional flow remains the same.