On 30.03.2014 22:38, Kai Krakow wrote:
> poma <pomidorabelis...@gmail.com> schrieb:
>
>> On 30.03.2014 22:03, Kai Krakow wrote:
>>> Tom Gundersen <t...@jklm.no> schrieb:
>> ...
>>>>> Hm, so the segfault happens in glibc... It is triggered by us calling
>>>>> calloc(1, 88), which I think is a supported thing to do ;) At least as
>>>>> far as I can tell this is not a bug on our side...
>>>>
>>>> Out of interest, what precise glibc version are you using?
>>>
>>> # equery l glibc
>>> * Searching for glibc ...
>>> [IP-] [ ] sys-libs/glibc-2.17:2.2
>>>
>>> Gentoo has 2.{18,19} available but not marked stable yet.
>>
>> http://www.gnu.org/software/libc/
>> ...
>> Current Status
>>
>> The current stable version of glibc is 2.19. See the NEWS file in the
> ^^^^^^
> These are two different meanings of stable. A distribution cannot see the
> stability of a sole package as itself - it has to see it as a whole in
> context of other packages. Usually, this means some other packages may see
> bugs or strange behavior with the upstream stable version of glibc.
>
> Thus, it's not as easy as copy and pasting information from somewhere else.
> Once again... ;-)
>
>> glibc sources for more information.
>> ...
>>
>> $ rpm -q glibc
>> glibc-2.19.90-8.fc21.x86_64
>
Exactly, it's a matter of distro you're driving. :)
poma
_______________________________________________
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel
