I'm trying to use the new Debugger Intercept feature in 7.1.1 and cannot seem to get it working.

- changed the debugger mode to "intercept" in the DB manager \ environment and saved the environ.

- add my own code the the DEBUGGER_REPLACMENT stored procedure.

But when the debugger is called, my new code in DEBUGGER_REPLACMENT is never executed.

I bet I am just missing some link.

Do I need to replace some other debugger SYSOBJ records with my new prog : $DEBUGGER_REPLACMENT ?

The only doc i found (in the readme.wri) says that : "A program named DEBUGGER_REPLACEMENT is included as the program called when Intercept is chosen. "

Jeff

Jeff,

Can you check the spelling on that? Are you sure your proc is DEBUGGER_REPLACEMENT, not DEBUGGER_REPLACMENT?

We seem to have a found a bug with the debugger intercept in that the intercept flag is not recognised until the environment settings are saved again, so at initial login the intecept doesn't work until set_Env() has been used (e.g. by the Database Manager)

Once that's been done the debugger intercept works fine. We also found that DEBUGGER_REPLACEMENT was in the SYSENV SYSPROCSNAMES record, so we had to remove it from there and restart before we could compile our own version.

The Sprezzatura Group

World leaders in all things RevSoft

Jeff and Sprezz-

We found an issue with Initialize and saving the debugger settings on boot up, and will have a patch quickly.

Mike

All-

We believe we've corrected this issue.

For beta users, we've uploaded this change to the beta section, and will make it available once it has passed testing.

Thanks

appears to init just fine now.

DSig

View this thread on the Works forum...