Re: [libvirt] Segfault in libvirtd when run as a service

On Thu, Jun 10, 2010 at 5:02 PM, Matthias Bolte < matthias.bolte(a)googlemail.com&gt; wrote: > 2010/6/10 Emre Erenoglu <erenoglu(a)gmail.com&gt;: > The initscript explicitly starts the one in /usr/sbin. If you just > start libvirtd manually without an absolute path then you'll start the > one in /usr/local/sbin. This might explain why you cannot reproduce > the segfault manually, but it doesn't explain why the segfault > happens. > There's no other installation of libvirt in the system. I can also reproduce the same thing in all Pardus machines, so I believe it's something in libvirt not doing well with something else in our service init mechanisms.

> >> Could you provide a GDB backtrace of the segfault? The syslog entry only > >> says that it crashed in libc, that's not enough information to > >> debug the segfault. > > > > Unfortunately, I can't find a related core file in the system. In fact, > core > > file is not generated. I'll also try to fix this out and come back to the > > list. > > > > Getting a backtrace would be simpler if you could reproduce the > problem manually. In that case you could just start libvirtd in GDB. > But getting a backtrace from a coredump will work too. > I can't reproduce the segfault when I run it manually. It only happens when it's run from this python script. I will try to initialize gdb inside the script and connect remotely to the gdb session, but it's getting a bit over my debugging capabilities :) For example, I don't know how to assign the symbols and source code etc from the package build directory to gdb.