> For the varargs and libc-forwarded function in msvcrt, I think all
> that we
> need is already in out spec file. So no need for the MS SDK.
If you want to write the tracing code by hand, yes. If you have the
headers winedump will generate the TRACE() statements for you as
well.
Cheers,
Jon
==
Uwe Bonnes <[EMAIL PROTECTED]> writes:
> in msvcrt a lot of functions are of type vararg (e.g. printf) or are
> forwards into the Linux libc (e.g. strstr) and so leave no trace in a +relay
> log. This makes it harder to debug.
The forwards into libc show up in relay just fine, they are not
differ
Hi Uwe,
>I think it would be helpfull, if we could generate debug stubs for
>these functions. Can anybody help?
If you have the SDK headers, winedump in spec mode can generate this
for you.
Cheers,
Jon
=
"Don't wait for the seas to part, or messiahs to come;
Don't you sit around and waste
> "Jon" == Jon Griffiths <[EMAIL PROTECTED]> writes:
Jon> Hi Uwe,
>> I think it would be helpfull, if we could generate debug stubs for
>> these functions. Can anybody help?
Jon> If you have the SDK headers, winedump in spec mode can generate
Jon> this for you.
For the va
Hallo,
in msvcrt a lot of functions are of type vararg (e.g. printf) or are
forwards into the Linux libc (e.g. strstr) and so leave no trace in a +relay
log. This makes it harder to debug.
I think it would be helpfull, if we could generate debug stubs for these
functions. Can anybody help?
Bye
-
