Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Mon, 8 Apr 2013 16:39:30 -0500
From: "jfoug" <jfoug@....net>
To: <john-dev@...ts.openwall.com>
Subject: RE: New addition to JtR.  memdbg, self-validating  memory management functions

I forgot to mention.  This is currently in a separate get branch, memdbg.  This is equivalent to bleeding, but with memdbg fully running.  The changes have been squashed into a single commit my Magnum.  There were a lot more than 1 commit, but since this has been done as a private project, until it was properly integrated into JtR code (and working), many of the changes would not have context.

Note, however, that numerous leaks, and bugs were found building this code. It should be good at keeping new code cleaner, at least in relationship to memory resources.  

Sent: Monday, April 08, 2013 15:13 From: jfoug@....net

> Introducing memdbg for JtR. 

... big clip ... 

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.