[Bug 18800] Winedbg has a race condition
wine-bugs at winehq.org
wine-bugs at winehq.org
Fri Jun 5 20:05:35 CDT 2009
http://bugs.winehq.org/show_bug.cgi?id=18800
--- Comment #6 from Todd Chester <ToddAndMargo at verizon.net> 2009-06-05 20:05:35 ---
Hi Ken,
I am using "/usr/bin/gnome-system-monitor". Both 123 and the debugger show
zero cpu. Actually, everything shows zero CPU, so I think that the race is so
bad that gnome-system-monitor can not update. You get one shot to kill 123 or
the gnome-system-monitor freezes up too. You get one shot with Gimp's screen
shot too and then it freeze up as well. Then you have to open an xterm and do a
"ps ax | grep -i 123" and a "kill -9". (After the "kill" everything that froze
comes back to life.)
The reason I think there is a race is that gnome-system-monitor shows 123.exe
being linked to the debugger. I could be wrong now. Would not be the first
time. (Into everyone's life a little humility must fall.)
This should be pretty easy to reproduce. Do you have 123?
-T
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
Do not reply to this email, post in Bugzilla using the
above URL to reply.
------- You are receiving this mail because: -------
You are watching all bug changes.
More information about the wine-bugs
mailing list