Join The Works program to have access to the most current content, and to be able to ask questions and get answers from Revelation staff and the Revelation community

At 25 SEP 2007 12:15:46PM Richard Hunt wrote:

I am using DEBUGGER_REPLACEMENT. Got some questions…

1) If I use a DEBUG statement, the DEBUTTER_REPLACEMENT is called for each sentence (line) executed. Is there a way to stop this? I mean something like the "RUN" button in the debugger? Or is there a NODEBUG statement???

2) Does anyone else have info or suggestions on how to trap multiple DEBUGGER_REPLACEMENT calls? Like well over 100 calls a minute. I think this results in new code that might have a bug in it.

3) I have started to save DEBUGGER_REPLACEMENT calls to a folder called ERRORS. Although I do not want thousands of rows in the ERRORS table before I can be notified of a single problem. I have played with the common variables for DEBUGGER_REPLACEMENT, they seem to have minimal information.

4) I was thinking that whe there is a call to the DEBUGGER_REPLACEMENT routine, that I could either close the window and processes, or even cause the user to exit OI. Kinda rough although I am not too sure I want to allow users to make thousands of calls to the DEBUGGER_REPLACEMENT routine.

Any suggestions would be appreciated. I just simply do not have any experience with this subject.


At 26 SEP 2007 10:15AM dsig@sigafoos.org wrote:

1 - I don't believe there is any way to 'cancel' the replacement.

2 - Since each call is independant it appears to have to just work through each call. You might want to add a couple of LC of your own which would include last time hit and program info (from program stack?) then if within a X amount of time simply exit out ???

3 - basically same as 2 .. yes?

4 - this would be a good concept. Some method of telling 'debug' to ignore any calls from program x (list of routines), as i don't think you want to turn off debug completely. Maybe a 'time' to ignore.

View this thread on the Works forum...

  • third_party_content/community/commentary/forums_works/037b30d958d5da5f852573610059559c.txt
  • Last modified: 2023/12/30 11:57
  • by 127.0.0.1