How does this actually work in practice?
I suppose altering instruction count or size still dooms the executable to become non-functional?
Or do all absolute & relative code & data references all get magically updated?
elf and pe have relocation info so u can patch things effectively. binary blobs might be problematic but project targets elf/pe from what i can tell.
there is no magic in computer -_-
HN does not seem to have discussed ddisasm enough.
When I discovered it, I was amazed, astonished, stunned, thrilled, and in disbelief.
It turns out that it actually works.
Why is it amazing?
ooh souffle! wonder how they avoid saturation explosion. that's doomed my souffle projects in the past. but obviously they've found a way to partition (maybe by block?)
500 Code(3)
Error: Code(3)
How does this actually work in practice?
I suppose altering instruction count or size still dooms the executable to become non-functional?
Or do all absolute & relative code & data references all get magically updated?
elf and pe have relocation info so u can patch things effectively. binary blobs might be problematic but project targets elf/pe from what i can tell.
there is no magic in computer -_-
HN does not seem to have discussed ddisasm enough.
When I discovered it, I was amazed, astonished, stunned, thrilled, and in disbelief.
It turns out that it actually works.
Why is it amazing?
ooh souffle! wonder how they avoid saturation explosion. that's doomed my souffle projects in the past. but obviously they've found a way to partition (maybe by block?)