The backtrace of the hang. Bacause the hang bring not the focus back to gdb, I was force the press the <CRTL-C> key. Only then, I was able to enter the final gdb commands which produced the log: backtrace full info registers thread apply all backtrace
a screendump is also provided before I pressed the <CRTL-C> key, it shows perfectly the hang consumes all CPU time and the application is not responsive anymore. Hope this helps to solve this bug ** Attachment added: "backtrace log" http://launchpadlibrarian.net/14863046/gdb-gnome-nettool.txt -- hangs after whois 88.198.41.48 https://bugs.launchpad.net/bugs/234747 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
