At 12:04 PM 14/03/2001 -0500, you wrote:
I remember wishing fondly for something like this when we were working on WordPerfect, but never having the time to do it myself.
FYI someone at Codeweavers has something much more sophistificated than my simple patch but from my understanding it's not ready for general use :-/
Gerard
At 12:04 PM 14/03/2001 -0500, you wrote:
I remember wishing fondly for something like this when we were working on WordPerfect, but never having the time to do it myself.
FYI someone at Codeweavers has something much more sophistificated than my simple patch but from my understanding it's not ready for general
use :-/
That would probably be my modification that allowed an external application to drive the debugging by extending the XClientMessage by adding a new Atom, wineDebug. It has the possibility to be more sophisticated than trapping on a function key, but for my purposes I limited it to just a few functions, ping, dumping the window list, and adding an entry into the log file so that I could mark the start and stop of an area of interest. It was something quick and dirty to solve a specific problem, so I did not submit it for inclusion into wine. I originally did use a keyboard interface, but needed something extensible allowing for more than just dumping a window list, hence went to more of a programmatic interface.
My current design is to have yet another dll that would register itself as the handler for this XClientMessage, so that on reciept of the XClientMessage, it is simply passed to this new dll. This dll would implement whatever application specific debugging tools I need, with only the bare minimum of support from wine needed. Since the wine debugger already has quite a bit of the functionality that is needed, it might be interesting if this method could be used to effectively open a pipe and drive the wine debugger externally.
-
gerard patel -
Rob Farnum