Re: thread problem with libc for Linux

Alexandre Oliva (aoliva@redhat.com)
13 Apr 2001 21:15:13 -0300


On Apr 13, 2001, Jerry Hong <jhong001@yahoo.com> wrote:

> Program received signal SIGSEGV, Segmentation fault.
> 0x401ca0d6 in chunk_free (ar_ptr=0x4025ed60,
> p=0x80a1ba8) at malloc.c:3097

This is usually a symptom of memory corruption in your own program.
It's damaging libc's internal data structures. I.e., this probably
has nothing to do with GCC or the kernel.

-- 
Alexandre Oliva   Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/
Red Hat GCC Developer                  aoliva@{cygnus.com, redhat.com}
CS PhD student at IC-Unicamp        oliva@{lsd.ic.unicamp.br, gnu.org}
Free Software Evangelist    *Please* write to mailing lists, not to me
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/