[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: glibc problem ?



Rogério Brito wrote:
> On Nov 20 2005, Benjamin Herrenschmidt wrote:
> 
>>On Sat, 2005-11-19 at 13:34 +0100, Yves-Alexis Perez wrote:
>>
>>>*** glibc detected *** free(): invalid pointer: 0x108979f0 ***
>>
>>This has nothing to do with glibc itself. glibc is basically warning
>>you that the application has corrupted memory. So something is wrong
>>in the app / libraries you are using.
> 
> 
> I don't remember exactly what caused it (it was three or four days ago),
> but I saw this same message in a i386 box (which I am using right now).
> 
> I have never seen this before and have not changed the system in any
> drastic way that would cause programs to behave incorrectly regarding
> memory allocation.
> 
> Oh, wait. Perhaps I did. I enabled 4k stacks in my latest kernel
> compilation (currently using 2.6.14.2).

It seems to be a "known" bug on gphoto2. The same thing occurs on a
vanilla 2.6.14 and on debian 2.6.14-2-powerpc


-- 
Yves-Alexis Perez
http://www.corsac.net

Attachment: signature.asc
Description: OpenPGP digital signature


Reply to: