On Wed, Oct 27, 2010 at 11:32 AM, Allan McRae <[email protected]> wrote:
> On 27/10/10 13:25, Ng Oon-Ee wrote:
>>
>> On Wed, Oct 27, 2010 at 1:52 AM, Thomas Bächler<[email protected]>
>> wrote:
>>>
>>> Am 26.10.2010 03:38, schrieb Allan McRae:
>>>>
>>>> Another day, another glibc...
>>>>
>>>> This adjusts the static linking fix. The one previously used is a more
>>>> correct fix but appears incomplete. I have replaced this by a hack fix
>>>> that Fedora uses.
>>>>
>>>> I will leave this in [testing] a while. My concern is the previous
>>>> patch apparently fixed a bunch of segfault bugs in glibc and I am hoping
>>>> that these do not get reintroduced.
>>>>
>>>> If only upstream made a proper fix for this. Saying upstream is doing
>>>> not much about this bug would imply that they are doing something...
>>>
>>> Thomas not know bug. Computer still boot. Thomas happy. Hurray! Thomas
>>> sign off.
>>>
>>
>> Segfault detected. Happens with bauerbill's AUR component. I'll just
>> pastebin the backtrace.
>>
>> --> Searching for upgradable AUR packages...
>> *** glibc detected *** /usr/bin/perl: double free or corruption
>> (fasttop): 0x00007fcbc826cf60 ***
>> ======= Backtrace: =========
>> http://pastebin.com/mgkBjv5q
>>
>
> Is this new and does downgrading glibc to the version in [core] fix it?
>
Sorry, should have mentioned that, does not happen with glibc from
[core] (2.12.1-3)
