Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <22ecbd9cfa1f1860ee064bd7050f55aa@smtp.hushmail.com>
Date: Wed, 17 Apr 2013 01:09:22 +0200
From: magnum <john.magnum@...hmail.com>
To: john-dev@...ts.openwall.com
Subject: Re: Segfaults probably caused by DEBUG code in memory.c

This doesn't solve the other issue I just posted.

magnum

On 17 Apr, 2013, at 1:05 , "jfoug" <jfoug@....net> wrote:

> I simply removed the memory.h constant. I still allocate the same amount, just not using the 'private' constant from memory
> 
> Jim.
> 
> From: jfoug Sent: Tuesday, April 16, 2013 17:59
>> I will change how dynamic allocates the salt list data.  It should not be using a 'private' item from memory.h
>> 
>> From: Frank Dittrich Sent: Tuesday, April 16, 2013 17:23
>>> My fault:
>>> 
>>> dynamic_fmt.c:1800:  pSaltDataBuf = pNextSaltDataBuf = mem_alloc_tiny(MEM_ALLOC_SIZE*6, MEM_ALIGN_NON
>>> dynamic_fmt.c:1801:  nSaltDataBuf = MEM_ALLOC_SIZE*6;
>>> 
>>> I should have checked the usage of MEM_ALLOC_SIZE before suggesting the change.
> <JtR_Bleeding_Dynamic_MEM_ALLOC_SIZE.patch>


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.