On Wed, 12.11.14 13:55, Steven Noonan (ste...@uplinklabs.net) wrote: > On Wed, Nov 12, 2014 at 11:22 AM, "Jóhann B. Guðmundsson" > <johan...@gmail.com> wrote: > > > > On 11/12/2014 07:00 PM, Steven Noonan wrote: > >> > >> >What's the best way to approach debugging this issue? Should I do a > >> >debug build to get a better core dump and wait for this to happen > >> >again? > >> > > > > > > > Looks like a regression or dupe of [1] not sure why this bug has not been > > reopen since there is a recent comment there. > > > > Add your info and coredump there > > Thanks, I've done so. > > I'd like to understand in general how one debugs issues like this with > systemd. Given that it's /sbin/init, it's not easy to just attach a > debugger to it and poke around. Do people operate primarily on core > dumps of -O0 -g builds or something?
You can easily attach a debugger to PID 1. Just invoke "gdb" and then type "attach 1" and there you go. But yeah, I work almost exclusively with -O0 -g builds when developing systemd. Lennart -- Lennart Poettering, Red Hat _______________________________________________ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
