Using the Script Debugger in Runtime Mode

Yesterday, I handled a support case that asked about using the Dexterity Script Debugger at runtime and whether there was any performance issues having the Debug menu enabled when it was not being used to perform any logging. What we are talking about is adding the ScriptDebugger=TRUE setting into the Dex.ini to enable the Script Debugger at runtime mode as described in the Knowledge Base (KB) article below: Using the Script Debugger in runtime (KB 850487) Now, this facility is really useful for developers to test their code in a live environment, especially if they are working with cross dictionary development techniques which cannot be tested using the Dexterity Test Mode from the Dexterity Development Environment. If you include the debug information and source code in a dictionary, you can use breakpoints and pause the code and look at variables and table buffers, just like in the normal development environment. In fact you can do everything except edit the scripts. You can also use the methods in the quick tip post below to swap dictionary context between dictionaries if you need to work with more than one dictionary at a time: Quick Tip: Changing Dexterity Script Debugger Context So, to answer the question: There is no performance issues caused by having the Script Debugger active (so that the Debug menu is displayed). If you enable logging or profiling then there will be a minor performance overhead as the runtime has to perform additional work

Read more from the original source:
Using the Script Debugger in Runtime Mode