*** This bug is a duplicate of bug 164552 ***
https://bugs.launchpad.net/bugs/164552
Thanks for the bug report. This particular bug has already been reported
into our bug tracking system, but please feel free to report any further
bugs you find.
** Changed in: gnome-nettool (Ubuntu)
** Attachment added: the hang consumes all CPU time and the application is not
responsive anymore
http://launchpadlibrarian.net/14863053/backtrace-gnome-nettool.png
--
hangs after whois 88.198.41.48
https://bugs.launchpad.net/bugs/234747
You received this bug notification because you are a
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
Thanks for your bug report. Please try to obtain a backtrace of the hang
http://wiki.ubuntu.com/DebuggingProgramCrash and attach the file to the
bug report. This will greatly help us in tracking down your problem.
** Changed in: gnome-nettool (Ubuntu)
Importance: Undecided = Medium
With all respect a 'hang' does not produce a backtrace in my opinion. I could
be wrong
Bug can be easily reproduced.
My time is now limited but I promise I will look at it and do my best to
produce a backtrace.
--
hangs after whois 88.198.41.48
https://bugs.launchpad.net/bugs/234747
You
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/14698360/Dependencies.txt
** Attachment added: ProcMaps.txt
http://launchpadlibrarian.net/14698361/ProcMaps.txt
** Attachment added: ProcStatus.txt
http://launchpadlibrarian.net/14698362/ProcStatus.txt
--
hangs after
