Displaying 5 results from an estimated 5 matches for "trace_".
Did you mean:
trace
2002 Feb 21
1
Help tracing WINE funcion..
...EventCapture(), and I'm trying to see
what all (yikes!) calles SetCapture()
I started with
[rick@pc99 wine]$ grep -nri --include *.c setcapture *
to get all the c files with set capture.
So now that I've added more traces, that command outputs (basically):
controls/button.c:234: TRACE_(win)("Calling SetCapture in
button.c\n");
controls/button.c:235: SetCapture( hWnd );
controls/button.c:236: TRACE_(win)("Done with SetCapture in
button.c\n");
controls/combo.c:1197: TRACE_(win)("Calling SetCapture
(combo.c)\n");
controls/combo.c:1198: SetCap...
2008 Mar 03
4
Modifying macro names generated by dtrace -h
I''d like to prepend TRACE_ to the macro names generated by dtrace -h.
For example, change
POSTGRESQL_LWLOCK_ACQUIRE(arg0, arg1) to
TRACE_POSTGRESQL_LWLOCK_ACQUIRE(arg0, arg1) and still keep postgresql as
the provider name. The reason for doing this is to make it clear that
the macros are used for (D)tracing. In this part...
2005 Aug 18
2
Updated Patch to chan_agent.c for PREACKANNOUNCE
...in the DB,
"database show" shows a key of:
//Agents/1001 : 721001@internal;1001
On another machine, the DB shows _nothing_, yet the
AgentCallbackLogin application works correctly (logging agents in
and out), and shows the correct mapping on the CLI during a login.
Still, the DB has _no trace_ of the Agents. I can't explain the
difference in behavior, and would _love_ to have someone solve
that mystery for me.
I'm hoping that I am missing something obvious in the interaction
between the Queue command and the Agents channel, and that some
kind soul here will educate me. Otherwise...
2012 Dec 03
17
[PATCH 0 of 3] xen: sched_credit: fix tickling and add some tracing
Hello,
This small series deals with some weirdness in the mechanism with which the
credit scheduler choses what PCPU to tickle upon a VCPU wake-up. Details are
available in the changelog of the first patch.
The new approach has been extensively benchmarked and proved itself either
beneficial or harmless. That means it does not introduce any significant amount
of overhead and/or performances
2012 Mar 17
0
tryCatch interferes with traceback(), debugger(), dump.frames()....
...blem. In this case, debugger() and traceback() point
to stop(e), not to the call to runif(), which makes it harder to figure out
what went wrong.
In most languages-featuring-exceptions I have used, there is something like
"rethrow" which propagates the original error _including the stack trace_
after you are done cleaning up in your error handler. Actually in my
opinion that is a big reason why exceptions are a language feature in the
first place - to propagate out debugging information while allowing you to
clean up. So I am confused why tryCatch ends up obscuring the debugging
informati...