[LCP] glibc error

[Paul Gearon]

Another one that I've hit in the past was accidentally free()ing
memory more than once. That can lead to some downright weird errors in
some malloc implementations.

Paul

On Wed, May 7, 2008 at 12:33 AM, Sharwan Joram <sharwan.joram at gmail.com> wrote:
> Hi Ivan,
>            The Probable cause of this might be , either you are writing the
> memory beyond it's allocation limit or you are trying to use the memory
> after freeing it .
>
> Regards
> Basileis
>
>
> On 5/7/08, ivan <lagigliaivan at gmail.com> wrote:
>>
>> Hi All,
>>
>> This is my first time posting on this e-mail list. I'd like to
>> participate actively on this list.
>> Here we go!
>>
>> I'm making a little application and I'm using ncurses. After a while
>> using it, I receive the following error and the stack is shown:
>>
>> ***glibc detected*** malloc() : memory corruption
>>
>> Anybody knows when glibc throws this error??
>>
>> I'll appreciate your help!
>>
>> Thanks in advance!
>>
>>
>> ivan.
>>
>> _______________________________________________
>> This is the Linux C Programming List
>> :  http://lists.linux.org.au/listinfo/linuxcprogramming List
>
>
> _______________________________________________
> This is the Linux C Programming List
> :  http://lists.linux.org.au/listinfo/linuxcprogramming List
>
>