[systemd-devel] [212] systemd-networkd crashes with simple network config

[Kai Krakow]

Tom Gundersen <teg at jklm.no> schrieb:

> On Sun, Mar 30, 2014 at 6:07 PM, Kai Krakow <hurikhan77 at gmail.com> wrote:
>> Tom Gundersen <teg at jklm.no> schrieb:
>>
>>>> Starting it from command line shows:
>>>>
>>>> # /usr/lib/systemd/systemd-networkd
>>>> enp4s0: link is up
>>>> enp4s0: carrier on
>>>> segmentation fault (core dumped)
>>>
>>> If you could reproduce this with debug symbols included, that would be
>>> very helpful (I cannot reproduce it here).
>>
>> I managed to get at least this backtrace. Somehow gdb did not autoload
>> the symbols for systemd from /usr/lib/debug/usr/lib/systemd...
>>
>> It is probably more helpful now (at least I hope).
>>
>> #0  0x0000003c49a82a7d in __libc_calloc (n=<optimized out>,
>> elem_size=<optimized out>) at malloc.c:3172
>>         av = 0x3c49da9640 <main_arena>
>>         oldtop = 0x6884d0
>>         p = <optimized out>
>>         bytes = 88
>>         sz = 88
>>         csz = <optimized out>
>>         oldtopsize = 23344
>>         mem = 0x6715f0
>>         clearsize = <optimized out>
>>         nclears = <optimized out>
>>         d = <optimized out>
>>         hook = <optimized out>
>>         __func__ = "__libc_calloc"
> 
> 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...

Probably the actual bug happened before because memory has been trashed, 
like by writing too many bytes into a too small buffer.

If you instruct me how to get something useful out of valgrind for you, I'm 
happy to help.

-- 
Replies to list only preferred.