Juan Lang wrote:
>> Ok when I put +relay on I get alot of other stuff I am not looking for...
>
> Sure. Some Windows APIs call other Windows APIs. +relay almost
> always produces too much information, but guessing which debug channel
> you really want is hard. Sometimes you have to read the rel
> Ok when I put +relay on I get alot of other stuff I am not looking for...
Sure. Some Windows APIs call other Windows APIs. +relay almost
always produces too much information, but guessing which debug channel
you really want is hard. Sometimes you have to read the relay channel
to guess which
Juan Lang wrote:
>> So is there any way to output just the win32 API calls and no wine
>> information.
>
> That's precisely what +relay does. I'm not sure what you mean by "no
> wine information."
> --Juan
Ok when I put +relay on I get alot of other stuff I am not looking for...
So what I am loo
> So is there any way to output just the win32 API calls and no wine
> information.
That's precisely what +relay does. I'm not sure what you mean by "no
wine information."
--Juan
Austin English wrote:
> On Wed, Jul 2, 2008 at 10:29 PM, Chris Ahrendt <[EMAIL PROTECTED]> wrote:
>> Is there a way within wine or wine debug to tell it to output just the
>> API's
>> which are being called? I am trying to debug a exception that causes an
>> application
>> to crash. As usual I do
On Wed, Jul 2, 2008 at 10:29 PM, Chris Ahrendt <[EMAIL PROTECTED]> wrote:
> Is there a way within wine or wine debug to tell it to output just the
> API's
> which are being called? I am trying to debug a exception that causes an
> application
> to crash. As usual I don't have the windows source c
On Wed, Jul 2, 2008 at 10:29 PM, Chris Ahrendt <[EMAIL PROTECTED]> wrote:
> Is there a way within wine or wine debug to tell it to output just the
> API's
> which are being called? I am trying to debug a exception that causes an
> application
> to crash. As usual I don't have the windows source c
Is there a way within wine or wine debug to tell it to output just the
API's
which are being called? I am trying to debug a exception that causes an
application
to crash. As usual I don't have the windows source code in order to
debug it that way.
So I was hoping there is a way within wine t
