On Wed, May 15, 2013 at 9:30 PM, Toralf Förster wrote:
> On 05/15/2013 09:11 PM, richard -rw- weinberger wrote:
>> On Wed, May 15, 2013 at 9:06 PM, Toralf Förster
>> wrote:
>>> On 05/13/2013 09:12 AM, richard -rw- weinberger wrote:
This looks like another issue.
Are you testing process
On 05/15/2013 09:11 PM, richard -rw- weinberger wrote:
> On Wed, May 15, 2013 at 9:06 PM, Toralf Förster
> wrote:
>> On 05/13/2013 09:12 AM, richard -rw- weinberger wrote:
>>> This looks like another issue.
>>> Are you testing process_vm_writev() with trinity?
>>> Looks like it managed to overwri
On Wed, May 15, 2013 at 9:06 PM, Toralf Förster wrote:
> On 05/13/2013 09:12 AM, richard -rw- weinberger wrote:
>> This looks like another issue.
>> Are you testing process_vm_writev() with trinity?
>> Looks like it managed to overwrite the stub page of a process, which
>> is not good.
> nope, it
On 05/13/2013 09:12 AM, richard -rw- weinberger wrote:
> This looks like another issue.
> Are you testing process_vm_writev() with trinity?
> Looks like it managed to overwrite the stub page of a process, which
> is not good.
nope, it is the mremap syscall.
A command like
$>trinity -c mremap -N
