This is the mail archive of the
cygwin-developers@cygwin.com
mailing list for the Cygwin project.
Re: State of the DLL, mark 2?
On Tue, Mar 20, 2001 at 04:27:19PM +0300, Egor Duda wrote:
>Tuesday, 20 March, 2001 Christopher Faylor cgf@redhat.com wrote:
>
>CF> Ok, I think we've fixed the rxvt hanging problem.
>
>CF> I haven't heard any further feedback on the hangs during build problem.
>
>CF> Is Cygwin still misbehaving when building a sources.redhat.com toolchain?
>CF> I tried this the other day and things seemed to be working ok except
>CF> for the -mwin32 problems.
>
>i've stumbled over it just now. sh traps in free() -- someone's
>corrupting the heap :(
>
>it's 100% reproducible, and it's traps with 1.1.6 too.
>
>i'm rebuilding cygwin1.dll with MALLOC_DEBUG now. Hopefully, we'll see
>who's corrupting the heap.
>
>btw, how big is MALLOC_DEBUG's penalty on performace? perhaps we
>should enable this if configured with --enable-debugging? or add
>--enable-malloc-debugging?
The penalty is huge. It makes things almost unusuable.
Btw, there are a lot of extra cruft that needs to be done to get this
working. I am attaching a malloc object file that you can use. I think
you also have to remove all malloc functions from newlib's libc.a.
cgf
dlmalloc.tar.bz2