On Wed, Jun 24, 2009 at 08:17:18AM +0200, Daniel Veillard wrote: > On Tue, Jun 23, 2009 at 03:28:40PM -0700, Garry Dolley wrote: > > On Tue, Jun 23, 2009 at 09:39:25PM +0100, Daniel P. Berrange wrote: > > > Install the -debug packages for libvirt, and get a trace > > > of all its threads under GDB, eg > > > > > > (gdb) thread apply all backtrace > > > > > > > > > Also, capture traces of the client & server, by setting LIBVIRT_DEBUG=1 > > > before running each. > > > > I solved the problem, but thanks for this info. I'll use it next > > time. > > > > How do I attach gdb to a running process? (I'm a gdb noob) > > gdb path_to_the_binary > > (gdb) attach pid_of_the_process > > this will attach to the process, load the debugging informations, stop > the process and get back to the gdb prompt for commands. Awesome, thanks! -- Garry Dolley ARP Networks, Inc. | http://www.arpnetworks.com | (818) 206-0181 Data center, VPS, and IP Transit solutions Member Los Angeles County REACT, Unit 336 | WQGK336 Blog http://scie.nti.st -- Libvir-list mailing list Libvir-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/libvir-list