James Hawkins wrote:
I don't know if you've ever wished the relay traces were indented by
the level of the call, so you can get a better feel for who calls what
from where, but I thought it would be nifty. I've attached a patch
> for dlls/ntdll/relay.c that gives you this.
Hah, funny..
I made
James Hawkins wrote:
On 6/24/06, Eric Pouech <[EMAIL PROTECTED]> wrote:
this won't work for a multithreaded program
tools/examine_relay does what you want, plus some other goodies (calls
that didn't return...)
Ah, didn't know about that tool. You learn something new every day.
It is also n
On Sat, 24 Jun 2006 02:15:09 -0700, James Hawkins wrote:
> Ah, didn't know about that tool. You learn something new every day.
Perhaps it should be mentioned in the developer quickstart.
thanks -mike
On 6/24/06, James Hawkins <[EMAIL PROTECTED]> wrote:
Ah, didn't know about that tool. You learn something new every day.
didn't know about that tool too. sounds interesting.
usually I do something like:
// reduce log size:
egrep -v
'RtlFreeHeap|RtlAllocateHeap|trace:syslevel:_Enter|trace:sy
On 6/24/06, Eric Pouech <[EMAIL PROTECTED]> wrote:
>
this won't work for a multithreaded program
tools/examine_relay does what you want, plus some other goodies (calls
that didn't return...)
Ah, didn't know about that tool. You learn something new every day.
IMO it's better to instrument the
James Hawkins wrote:
Hey guys,
I don't know if you've ever wished the relay traces were indented by
the level of the call, so you can get a better feel for who calls what
from where, but I thought it would be nifty. I've attached a patch
for dlls/ntdll/relay.c that gives you this. You see the
Hey guys,
I don't know if you've ever wished the relay traces were indented by
the level of the call, so you can get a better feel for who calls what
from where, but I thought it would be nifty. I've attached a patch
for dlls/ntdll/relay.c that gives you this. You see the call level
next to the
