Hi All
I''ve just started working with AccuTerm 8. x and as a developer, we sometimes need to break out of code that is processing to debug.
Yes, I could place a conditional debug statement in the code but het guess what "Real men don't do that" :)
Anyway - pressing all key sequences (that I know) bears no fruit so I've stopped guessing and put this fwd to this group.
I'm running Windows (10 and 11) and set my emulation to Viewpoint onto a Linux installed D3 10. x
Does anyone have the correct key sequence, please?
Thanks
Stefano
Hy i use this sequence
in TCL i do this:
SET-BREAK .7E
BRK-DEGUB
and start the program.. so any moment that i need to enter in the debuger i type ~
and it enters the debug mode without using the debug statement in the code and recompiling
the ~its represented by .7E with you wnat to use another key as debugger key.. just informe in
SET-BREAK (hexdecimal of the key)
Hi All
I''ve just started working with AccuTerm 8. x and as a developer, we sometimes need to break out of code that is processing to debug.
Yes, I could place a conditional debug statement in the code but het guess what "Real men don't do that" :)
Anyway - pressing all key sequences (that I know) bears no fruit so I've stopped guessing and put this fwd to this group.
I'm running Windows (10 and 11) and set my emulation to Viewpoint onto a Linux installed D3 10. x
Does anyone have the correct key sequence, please?
Thanks
Stefano
Thanks @Alberto Leal
I assume one can use "any" key (sequence).
The reason I ask is because I use the '~' as a delimiter and things would go horribly wrong if I set debug to that key :(
So, assuming a(any) key then I could do Ctl~ (and I would have to determine the hex value) and could get that to work.
I read this which is interesting - and we had that working with OpenInsight :
Ctrl + Fn + B or Fn + B on certain Dell laptops.
Hi All
I''ve just started working with AccuTerm 8. x and as a developer, we sometimes need to break out of code that is processing to debug.
Yes, I could place a conditional debug statement in the code but het guess what "Real men don't do that" :)
Anyway - pressing all key sequences (that I know) bears no fruit so I've stopped guessing and put this fwd to this group.
I'm running Windows (10 and 11) and set my emulation to Viewpoint onto a Linux installed D3 10. x
Does anyone have the correct key sequence, please?
Thanks
Stefano
yes.. you can set any key...
in my exemple i used .7e for ~
but you can use .20AC for ALT X
or you can you this basic program, to discovery the HEX that you want use for your keys
input x
crt seq(x)
y = seq(x)
crt char(y)
CRT OCONV(char(y),"MX")
Hi All
I''ve just started working with AccuTerm 8. x and as a developer, we sometimes need to break out of code that is processing to debug.
Yes, I could place a conditional debug statement in the code but het guess what "Real men don't do that" :)
Anyway - pressing all key sequences (that I know) bears no fruit so I've stopped guessing and put this fwd to this group.
I'm running Windows (10 and 11) and set my emulation to Viewpoint onto a Linux installed D3 10. x
Does anyone have the correct key sequence, please?
Thanks
Stefano
Hi Stefano,
We set the break level in the "USERS" file (at least in a linux implementation)
Attributes 12 and beyond are used to setup the environment for the current session.
We use two commands:
BRK-LEVEL
The brk-level command causes the BREAK key to push a level on subsequent uses. It is not possible to push a level while at the TCL prompt. At least one character must be entered.
On some systems, when the BREAK key is set to push a level, it is not possible to push a level while in the debugger. To push a level while in the debugger, type : and press ENTER.
SET-BREAK 3
set-break {decimal.value}|{.hexadecimal.value}|{off}|{esc}|{^} {(options}
In this case the 3 represents the 3rd ascii character or a ctrl-c
SET-BREAK OFF
Disable breaking out of a program
Setting these values in the USERS table for just your developers allows the developers to break out of programs while disabling the feature for standard users.
Depending on how your users record is setup, you will likely want to set these two items before most if not all other commands to be run at the session startup.
In our system, developers are setup starting like this: TERM-TYPE is executed first, followed by BRK-LEVEL and then SET-BREAK 3
Standard users are setup like this: TERM-TYPE, BRK-LEVEL, SET-BREAK OFF
Hope this helps.
Lance
Hi All
I''ve just started working with AccuTerm 8. x and as a developer, we sometimes need to break out of code that is processing to debug.
Yes, I could place a conditional debug statement in the code but het guess what "Real men don't do that" :)
Anyway - pressing all key sequences (that I know) bears no fruit so I've stopped guessing and put this fwd to this group.
I'm running Windows (10 and 11) and set my emulation to Viewpoint onto a Linux installed D3 10. x
Does anyone have the correct key sequence, please?
Thanks
Stefano
Hi @Lance Mcmillin
Your answer is valid and did similar once @Alberto Leal "showed me the way" :)
Thanks for "the confirmation" much appreciated :)
Stefano
Hi All
I''ve just started working with AccuTerm 8. x and as a developer, we sometimes need to break out of code that is processing to debug.
Yes, I could place a conditional debug statement in the code but het guess what "Real men don't do that" :)
Anyway - pressing all key sequences (that I know) bears no fruit so I've stopped guessing and put this fwd to this group.
I'm running Windows (10 and 11) and set my emulation to Viewpoint onto a Linux installed D3 10. x
Does anyone have the correct key sequence, please?
Thanks
Stefano
We use the default Ctrl
This give is a break to the debugger.
