On Wed, Nov 10, 2010 at 11:34:23AM +0000, Daniel P. Berrange wrote:
On Wed, Nov 10, 2010 at 11:01:15AM +0100, Daniel Veillard wrote:
With some instruction on how to attach useful gdb backtraces [...] + <pre> # ps -o etime,pid `pgrep libvirt` +... note the process id from the output +# gdb /usr/sbin/libvirtd +.... some informations about gdb and loading debug data +(gdb) attach $the_damon_process_id +.... +(gdb) thread apply all bt +.... informations to attach to the bug +(gdb) +</pre>
You don't need to specify the /usr/sbin/libvirtd binary name on the command line to GDB if you're about to use 'attach', because GDB will find it automatically from the PID, but ACK anyway
okay, just that I always do it that way, and since that's the only example of gdb usage on that page, being a bit more complete should not hurt :-) pushed ! Daniel -- Daniel Veillard | libxml Gnome XML XSLT toolkit http://xmlsoft.org/ daniel@veillard.com | Rpmfind RPM search engine http://rpmfind.net/ http://veillard.com/ | virtualization library http://libvirt.org/