This is the mail archive of the libc-help@sourceware.org mailing list for the glibc project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: Glibc 2.12 segfaults under certain conditions

From: Daniele stanzani <daniele dot stanzani at fcp dot it>
To: pocmatos at gmail dot com (Paulo J. Matos)
Cc: libc-help at sourceware dot org
Date: Wed, 13 Oct 2010 12:18:21 +0200
Subject: Re: Glibc 2.12 segfaults under certain conditions
References: <1282131799.4075.30.camel@localhost.localdomain><AANLkTik52W8gVayDDPohxKOargACT2P-341dobpvYdn=@mail.gmail.com><8639saif2q.fsf@pm18pc01.europe.root.pri>

On Wed, 13 Oct 2010 11:04:29 +0100
pocmatos@gmail.com (Paulo J. Matos) wrote:

> "Carlos O'Donell" <carlos@systemhalted.org>
> writes:
> >
> > In your case my first guess is bad memory on the machine.
> >
> 
> Unfortunately I am not sure this is the case. I just happened to face
> it after an upgrade to Ubuntu Maverick and I can consistently
> reproduce it. Although there are many things involved and you might
> be right, I find it awkward to be a memory problem in this specific
> case.
> 

Allan McRae from archlinux team made it out of this bug, but I do not
know how he did it or the patch he applied.

Please take a look at the bug I filed after requesting help at the libc
ml.

https://bugs.archlinux.org/task/20513

On Archlinux the problem is now solved.

-- 
Daniele Stanzani

Attachment: signature.asc
Description: PGP signature

Follow-Ups:
- Re: Glibc 2.12 segfaults under certain conditions
  - From: Paulo J. Matos

References:
- Re: Glibc 2.12 segfaults under certain conditions
  - From: Paulo J. Matos

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]