search for: trace_al

Hi all, I need some assistance.. I'm trying to trace a problem. The quick description is when I run the Visual FoxPro 5 development environment, and I click in a 'edit' window (like when you bring your program up, to edit it) the screen freezes. when I ran wine --debugmsg +win vfp.exe, my last line of trace is: trace:win:EVENT_Capture (0x20021) So I saw that SetCapure() called

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 particular case, without TRACE_, it appears like the macro is used

First, many thanks to Greg Boehnlein for his patch to chan_agent.c for adding a "preackannounce" option. I am running CVS HEAD from 2005/07/31, and the patch failed in a few hunks, since the code was refactored to add in some CASE statements where there were compound if statements before. Anyway, I have successfully updated the patch to work against head as of 3 weeks ago, and would

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

I want to use tryCatch, but tryCatch seems to obscure important things I need for debugging. For example, say I am working with an SQLite database, and have written this function: debugThisFunction <- function(dbfile) { require(RSQLite) drv <- SQLite() conn <- dbConnect(drv, dbfile) tryCatch({ dbBeginTransaction(conn) tryCatch({ for (i in 1:10) {