Dear Bill,
This seems unusual, and suggests that there's some memory corruption
going on somewhere. Any chance you can run this under valgrind and
send me the results?
sure, the following provides the valgrind --leak-check=full dump of the
following code snippet:
---
...
On 04/28/2014 05:37 PM, Sergej Proskurin wrote:
Dear Bill,
When you say this crashes with a segfault at the point of insertion,
do you mean the mutator crashes when inserting the code, or the
mutatee crashes when executing it? In either case, a stack trace will
be helpful; in the latter case
On 04/26/2014 03:28 PM, Sergej Proskurin wrote:
Hello,
Within my current implementation, I am able to split and inject basic
blocks on the basis of PatchAPI. The newly created and injected basic
blocks are currently filled with raw bytes, as stated within the following:
InsertedCode::Ptr icode
Dear Bill,
When you say this crashes with a segfault at the point of insertion,
do you mean the mutator crashes when inserting the code, or the
mutatee crashes when executing it? In either case, a stack trace will
be helpful; in the latter case if you're running the mutatee under
Dyninst
Hello,
Within my current implementation, I am able to split and inject basic
blocks on the basis of PatchAPI. The newly created and injected basic
blocks are currently filled with raw bytes, as stated within the following:
InsertedCode::Ptr icode = PatchModifier::insert(post_block-object(),
