Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <d6267608c7e5f029273509705c984256@smtp.hushmail.com>
Date: Mon, 8 Apr 2013 23:55:17 +0200
From: magnum <john.magnum@...hmail.com>
To: john-dev@...ts.openwall.com
Subject: Re: New addition to JtR.  memdbg, self-validating  memory management functions

On 8 Apr, 2013, at 23:39 , "jfoug" <jfoug@....net> wrote:

> I forgot to mention.  This is currently in a separate get branch, memdbg.  This is equivalent to bleeding, but with memdbg fully running.

Well it's currently not fully running as-is, you'd need to edit memdbg_defines.h and uncomment the define.

To try it out, do the above, then comment out some obscure free() somewhere in the code, build and do a --test=0. The cool thing compared to eg. Valgrind is that the performance penalty is negligible (at least in comparison).

magnum


Powered by blists - more mailing lists

Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.