Re: Why is our OutputDebugString a server request?

[Pouech Eric DMI AEI CAEN]

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?

Why is our OutputDebugString a server request?

[Shachar Shemesh]

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

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?

Shachar

Why is our OutputDebugString a server request?

[Alexandre Julliard]

Shachar Shemesh  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 debuggers
should be able to deal with it. The real Win32 way would be to raise
an exception, which is certainly something we could do; but since
Win32 provides a debug event for this purpose, it seemed reasonable to
use it. Now, if you know of a case where it causes trouble, it can be
changed.

Why is our OutputDebugString a server request?

[Shachar Shemesh]

Alexandre Julliard wrote:
> Shachar Shemesh  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 debuggers
> should be able to deal with it. The real Win32 way would be to raise
> an exception, which is certainly something we could do;

Not according to my information. According to my information, this is 
merely a mutex and an event. (is that what you meant?).

I'll do some proper looking into here.
> but since
> Win32 provides a debug event for this purpose, it seemed reasonable to
> use it. Now, if you know of a case where it causes trouble, it can be
> changed.

I get the feeling that I misunderstood what you just said. What is the 
debug event? where do we do anything with it?

Shachar