Bug#780675: systemd: segfault in systemd when running systemctl daemon-reload

[Robert Pumphrey]

On 17/03/15 21:07, Michael Biebl wrote:
> Am 17.03.2015 um 19:35 schrieb Michael Biebl:
>> Am 17.03.2015 um 19:05 schrieb Robert Pumphrey:
>
>>> #0  0x00007f8d3e06779b in raise (sig=11) at
>>> ../nptl/sysdeps/unix/sysv/linux/pt-raise.c:37
>>>          resultvar = 0
>>>          pid = <optimized out>
>>> #1  0x00007f8d3e4bd3d8 in ?? ()
>>> No symbol table info available.
>>> #2  <signal handler called>
>>> No locals.
>>> #3  0x00007f8d3e4422a0 in ?? ()
>>> No symbol table info available.
>>> #4  0x00007f8d3e4f8caa in ?? ()
>>> No symbol table info available.
>>> #5  0x00007f8d3e56777f in ?? ()
>>> No symbol table info available.
>>> #6  0x00007f8d3e55f558 in ?? ()
>>> No symbol table info available.
>>> #7  0x00007f8d3e4bac6b in ?? ()
>>> No symbol table info available.
>>> #8  0x00007f8d3dcd0b45 in __libc_start_main (main=0x7f8d3e4b6dd0,
>>> argc=1, argv=0x7ffd3c533ea8, init=<optimized out>, fini=<optimized out>,
>>> rtld_fini=<optimized out>, stack_end=0x7ffd3c533e98)
>>>      at libc-start.c:287
>>>          result = <optimized out>
>>>          unwind_buf = {cancel_jmp_buf = {{jmp_buf = {0,
>>> 5361389912737802513, 140244612264611, 140725615541920, 0, 0,
>>> -5360124553165444847, -5369135033269130991}, mask_was_saved = 0}}, priv
>>> = {pad = {0x0, 0x0,
>>>                0x7ffd3c533eb8, 0x7f8d3e4971a8}, data = {prev = 0x0,
>>> cleanup = 0x0, canceltype = 1012088504}}}
>>>          not_first_call = <optimized out>
>>> #9  0x00007f8d3e4bb2cc in ?? ()
>>> No symbol table info available.
>>
>> Hm, nothing interesting/relevant in there. Almost as if the symbols do
>> not match the binary/core dump or the crash is not in systemd itself.
>
> Do you have systemd-dbg installed?
>
>
>
I have identified a duff init.d script (one of our own that previously 
worked in wheezy) that is at the root of this problem. I have removed 
the script, rebooted and the I can now run systemctl daemon-reload 
withough a seg fault.
This bug may just indicate that systemd poorly handles a bad init 
script. Please let me know if you would like details of our broken 
script, otherwise, I am happy for this to be closed.

Thank you for your patience in helping me report this problem.