At 01:48 PM 5/21/00 +0000, you wrote:
Just to prove that someone has looked at your work :-)
>+This allows to redirect all WineDbg output to both tty Wine was
>+started from, and xterm debugging window. If Wine (or WineDbg) was
>+started with a redirection of stdout and/or stderr to a file (with for
>+example >& shell redirect command), you'll get in that file both
>+outputs. It may be interesting to look in the relay trace for specific
>+values which the process segv:ed on.
Have you (or anyone) ever tried to run the debugger through a serial line ? I am
thinking of trying this since quite a time but have never found the time.
It would be neat to be able to debug painting problems without the
switching to term or xterm forcing repaint messages in Wine.
>+mode 16 switch to 16 bit mode
>+mode 32 switch to 16 bit mode
typo :-)
And what is the use of mode16, anyway ? You say later that 16 bit debugging
is not supported ? Is it necessary to use mode16 before a callback to 16 is
done ?
<snip available commands>
I'm afraid that the old doc (README in debugger/ and documentation/debugging)
is now slighly outdated.
>+- you need oo attach the unix debugger to the correct unix process
typo :-)
As a general comment, it would be neat if some trick allowed to start
the debugger in a separate space before launching the program to
debug (wine -debug maybe :-))
Gerard
