hangs after whois 88.198.41.48

Bug #234747 reported by Michael
0
Affects Status Importance Assigned to Milestone
gnome-nettool (Ubuntu)
Invalid
Medium
Ubuntu Desktop Bugs

Bug Description

Binary package hint: gnome-nettool

gnome-nettool hangs after query whois (last tab) of the following ip address : 88.198.41.48
a manual whois in the terminal of this ip address is no problem
The 'hang' produces a 100% cpu usage too (measured with top in a separate terminal)

ProblemType: Bug
Architecture: i386
Date: Sun May 25 12:39:34 2008
DistroRelease: Ubuntu 8.04
ExecutablePath: /usr/bin/gnome-nettool
NonfreeKernelModules: nvidia
Package: gnome-nettool 2.22.0-0ubuntu2
PackageArchitecture: i386
ProcEnviron:
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=nl_NL.UTF-8
 SHELL=/bin/bash
SourcePackage: gnome-nettool
Uname: Linux 2.6.24-17-generic i686

Tags: apport-bug
Revision history for this message
Michael (m-gruys) wrote :
Revision history for this message
Pedro Villavicencio (pedro) wrote :

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:
assignee: nobody → desktop-bugs
importance: Undecided → Medium
status: New → Incomplete
Revision history for this message
Michael (m-gruys) wrote :

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.

Revision history for this message
Michael (m-gruys) wrote :

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

Revision history for this message
Michael (m-gruys) wrote :
Revision history for this message
Pedro Villavicencio (pedro) wrote :

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:
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.