'glibc detected - double free or corruption'

[theart at adib.nl (Arthur Donkers)]

Hi,

I ran into the same problem when using scanrand2 on Fedora Core 3. The
solution is to set MALLOC_CHECK_ to 0 (zero) and not to 1 like thus:

export MALLOC_CHECK_=0

The glibc of Fedorea Core 3 seems to have been compiled with ultra paranoid
set so any free that looks suspicious will generate this error and kill
the 'offending' process.

Goog luck,

Arthur

On Sat, June 4, 2005 0:52, Anthony Riehm said:
> Running the Framework on Fedora Core 3; when trying to perform an exploit
> it
> (seemingly randomly) will begin the process and then stop with an error
> that
> says,
>
> *** glibc detected *** double free or corruption (!prev): 0x0912d4d0 ***
>
> This happens on versions 2.2, 2.3, and 2.4 of Framework... but it doesn't
> do
> it every single time.
>
> I did a search for that error message and other people have had that
> problem
> on Fedora Core 3, in other programs. One person suggested doing:
>
> export MALLOC_CHECK_=1
>
> but even this didn't fix the problem; I just got other errors.


-- 
/* Disclaimer :   you hire my skills, not my opinions, those are mine !  */
/* email : theart at adib.nl      Security    'Me ? I'm not me ! I'm just a */
/* phone : (+31) 595 557057    is not a     computer simulation of me'   */
/* URL http://www.adib.nl     dirty word      Red Dwarf, First Episode   */