[systemd-devel] Possible systemd segfault switching from 216 to 219 in fedora upgrade

[James Hogarth]

On 5 March 2015 at 15:10, Lennart Poettering <lennart at poettering.net> wrote:
>
>
> Right before switch rooting systemd will kill all remaining processes
> of the initrd, including the strace, hence the strace logs aren't that
> useful either, they end before the transition.
>
> Please boot with "systemd.log_level=debug systemd.log_target=kmsg" on
> the kernel cmdline, which ensures the logs go to the kernel log
> buffer. And then please provide the output this generates here.
>
> Also see:
>
> http://freedesktop.org/wiki/Software/systemd/Debugging/
>
>

Thanks Lennart - good point about the strace being killed before the
interesting bit...

This makes it annoyingly tricky to see what is happening as the
systemd-219 binary gets loaded...

Screenshot has been attached to the bug:

https://bugzilla.redhat.com/show_bug.cgi?id=1185604#c22

Doesn't show much though - just a SEGV reported by pid1 that
immediately results in execution being halted.

Tried to put together a reduced testcase via a yum installroot style
container to switch-root into to see what that behaviour is like and
do see a segfault - not certain if this is the same being seen during
the fedup switch-root though...

Any ideas to get a better grasp on this?