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%?