http://bugs.winehq.org/show_bug.cgi?id=18800
Summary: Debugger goes into race condition after 123 crash on bug 18324 Product: Wine Version: 1.1.23 Platform: PC OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P3 Component: dbghelp AssignedTo: wine-bugs@winehq.org ReportedBy: ToddAndMargo@verizon.net
Hi All,
Please reference bug 18324 on this bug. This is bug is on the debugger and 18324 in on Lotus 123.
Basically, when you try to copy from two cell into the clip board in Lotus 123, 123 will crash (bug 18324). And, the debugger goes into a race condition, eating up as much CPU as the OS will give it. It never finished. The only way to stop the race is tho do a "kill -9" on 123's process ID.
-T
Steps to reproduce: 1) open the 123 attachment on 18324 (http://bugs.winehq.org/attachment.cgi?id=20865)
2) highlight across two cell horizontally
3) press <ctrl><c> or go to "Edit", "Copy"
http://bugs.winehq.org/show_bug.cgi?id=18800
Ken Sharp kennybobs@o2.co.uk changed:
What |Removed |Added ---------------------------------------------------------------------------- Component|dbghelp |-unknown Summary|Debugger goes into race |Lotus 123 crashes when |condition after 123 crash |trying to copy two cells |on bug 18324 |
http://bugs.winehq.org/show_bug.cgi?id=18800
--- Comment #1 from Ken Sharp kennybobs@o2.co.uk 2009-06-05 18:55:44 --- What version of Lotus 123?
Can you attach the console output, whatever it looks like?
http://bugs.winehq.org/show_bug.cgi?id=18800
Ken Sharp kennybobs@o2.co.uk changed:
What |Removed |Added ---------------------------------------------------------------------------- Keywords| |source Summary|Lotus 123 crashes when |Winedbg has a race |trying to copy two cells |condition
--- Comment #2 from Ken Sharp kennybobs@o2.co.uk 2009-06-05 19:08:18 --- Hmmm, OK, I see what you're doing now, changed the title.
I can't see this not being a duplicate of bug 18324, but the console output would help decide.
http://bugs.winehq.org/show_bug.cgi?id=18800
--- Comment #3 from Todd Chester ToddAndMargo@verizon.net 2009-06-05 19:45:14 --- Created an attachment (id=21587) --> (http://bugs.winehq.org/attachment.cgi?id=21587) Screen Shot of debugger crash
Smart Suite version N9.8.0208.1200
I see this as two bugs. The first one is 18324, which is the crash in 123 when you try to copy two cells into the clipboard. The second is the debugger that goes crazy after the crash. I guess you could combine the two bugs as 18800 will be impossible to reproduce when 18324 gets fixed.
My computer acts really, really weird until you do a "kill -9" on 123.exe.
-T
http://bugs.winehq.org/show_bug.cgi?id=18800
--- Comment #4 from Ken Sharp kennybobs@o2.co.uk 2009-06-05 19:51:13 --- That's not helpful, we need the console output. http://wiki.winehq.org/FAQ#get_log
The debugger can use 100% CPU for a short while, but shouldn't do so for a long period of time.
Have you confirmed in top that it is winedbg that is running at 100%?
http://bugs.winehq.org/show_bug.cgi?id=18800
--- Comment #5 from Ken Sharp kennybobs@o2.co.uk 2009-06-05 19:54:01 --- (In reply to comment #4)
That's not helpful, we need the console output. http://wiki.winehq.org/FAQ#get_log
Actually, a +winedbg trace might confirm if the race condition exists.
http://bugs.winehq.org/show_bug.cgi?id=18800
--- Comment #6 from Todd Chester ToddAndMargo@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
http://bugs.winehq.org/show_bug.cgi?id=18800
Ken Sharp kennybobs@o2.co.uk changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |kennybobs@o2.co.uk
--- Comment #7 from Ken Sharp kennybobs@o2.co.uk 2009-06-05 20:23:18 --- I have an old version of Smartsuite laying around somewhere, if I can find it, I'll give it a try, but this probably won't be for a couple of days.
The +winedbg trace will still help here.
It is unlikely that any app will stop top from updating, and it's default layout will put the busiest app at the top. I would recommend using it.
http://bugs.winehq.org/show_bug.cgi?id=18800
--- Comment #8 from Todd Chester ToddAndMargo@verizon.net 2009-06-05 20:51:25 --- Man the bugzilla is getting testy: it is making me sign in every time I click on anything new.
I think at this point it would be the better part of wisdom to let you locate your Smart Suite. If you can reproduce the bug, you will know better than me what is happening.
http://bugs.winehq.org/show_bug.cgi?id=18800
--- Comment #9 from Ken Sharp kennybobs@o2.co.uk 2009-08-09 11:03:30 --- OK, found my discs but my 123 is the old 97 edition which isn't affected by Bug 18324.
Please attach a +winedbg trace. http://wiki.winehq.org/FAQ#head-16da35b6327024d6ea576e3678488b16862d0f5e
http://bugs.winehq.org/show_bug.cgi?id=18800
--- Comment #10 from Todd Chester ToddAndMargo@verizon.net 2009-08-09 20:19:09 --- No need for the trace. I am unable to reproduce this under Wine 1.1.27. This bug was a total pain in the, eh, well, neck. Thank you guys so, so much!
Please close this ticket as "FIXED". YIPEE!
-T (the "Original Poster")
http://bugs.winehq.org/show_bug.cgi?id=18800
--- Comment #11 from Todd Chester ToddAndMargo@verizon.net 2009-08-09 20:23:17 --- (In reply to comment #9)
Please attach a +winedbg trace. http://wiki.winehq.org/FAQ#head-16da35b6327024d6ea576e3678488b16862d0f5e
Hi Ken,
Thank you giving me a link to how you want the trace done. It is a nice touch. And, it cuts down on the frustration when asked for a trace. There are a lot of different, confusing options in a trace.
-T
http://bugs.winehq.org/show_bug.cgi?id=18800
Ken Sharp kennybobs@o2.co.uk changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution| |FIXED
--- Comment #12 from Ken Sharp kennybobs@o2.co.uk 2009-08-09 20:32:39 --- Glad to see it's fixed.
http://bugs.winehq.org/show_bug.cgi?id=18800
Alexandre Julliard julliard@winehq.org changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #13 from Alexandre Julliard julliard@winehq.org 2009-08-21 12:51:58 --- Closing bugs fixed in 1.1.28.
https://bugs.winehq.org/show_bug.cgi?id=18800
brewmanz brewmanz@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |brewmanz@gmail.com
-
wine-bugs＠winehq.org