Shachar Shemesh wrote:
Hi all,
It seems that OutputDebugString is defined in the Win32 API as a set
of client side operations. In wine, however, it is a server request.
I have not traced it into the server to see whether they carry out the
same operations or not. However, even if they do, I am w
> I get the feeling that I misunderstood what you just said. What is the > debug event? where do we do anything with it?debug events are part of the Win32 debug API. A debugger (ie a process using the client side of this API) will get "debug events" (basically the type of the event and some additi
Alexandre Julliard wrote:
Shachar Shemesh <[EMAIL PROTECTED]> writes:
But as far as I can see, this means that Windows debuggers won't get
it. Wouldn't it be better to implement it the Win32 way? At the very
least, implement it ALSO as the Win32 way?
It will generate an output string debug
Shachar Shemesh <[EMAIL PROTECTED]> writes:
> But as far as I can see, this means that Windows debuggers won't get
> it. Wouldn't it be better to implement it the Win32 way? At the very
> least, implement it ALSO as the Win32 way?
It will generate an output string debug event, so Windows debugger
Title: RE: Why is our OutputDebugString a server request?
I agree - I got stumped on this very issue when I got into Wine last year. I was used to relying on these trace messages and it took me a while to understand where the messages were actually being sent!
//raghavan
-Original
Pouech Eric DMI AEI CAEN wrote:
so that debuggers can intercept it (especially ones with GUI) and do
what they want with it.
A+
> Message du 13/09/04 17:50
> De : "Shachar Shemesh"
> A : "Wine Development"
> Copie à :
> Objet : Why is our OutputDebugString a server request?
so that debuggers can intercept it (especially ones with GUI) and do what they want with it.A+
> Message du 13/09/04 17:50> De : "Shachar Shemesh" <[EMAIL PROTECTED]>> A : "Wine Development" <[EMAIL PROTECTED]>> Copie à : > Objet : Why is our OutputDebugString a server request?>
