[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <loom.20131227T204354-150@post.gmane.org>
Date: Fri, 27 Dec 2013 19:44:23 +0000 (UTC)
From: David Wuertele <dave+gmane@...rtele.com>
To: musl@...ts.openwall.com
Subject: Re: NULL deref SEGV in malloc.c:unbin()
Rich Felker <dalias <at> aerifal.cx> writes:
> On Fri, Dec 27, 2013 at 06:35:00PM +0000, David Wuertele wrote:
> > I wonder if anyone has hit this before? In unbin(), c->next->prev is set,
> > but c->next is NULL. It happens repeatedly, and here's what gdb says:
>
> It's almost surely a case of memory corruption by the calling program,
> most likely using memory after it's already been freed.
Hmm, my program calls malloc() once and never calls free().
Oh, I guess it does call free indirectly when it uses closedir() and fclose().
I will try to use gdb/watch to catch someone red-handed.
Dave
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.
