Debugger is not showing all the trace tabs when suspension occurs in some client/server combinations

[dyaandys]

]udebug on
]settings -
macOS: see just one tab with SaltinSpice. No sign of UCMD, nor of intermediate functions
Windows client to windows APL: same

IDE:
Version: 4.0.2834
Platform: Win32
Date: 2017-06-20 13:42:27 +0100
Git commit: 2d04452
Preferences:{
"favs":"[{"type":"connect","ssh_auth_type":"pass","ssh_tnl_auth_type":"pass","name":"debian7dev","host":"debian7dev.dyalog.bramley","port":"4502"},{"type":"connect","ssh_auth_type":"pass","ssh_tnl_auth_type":"pass","name":"dfsaix","host":"10.0.61.100","port":"9003"},{"ssh_auth_type":"pass","ssh_tnl_auth_type":"pass","name":"mac0","host":"mac0"},{"ssh_auth_type":"pass","ssh_tnl_auth_type":"pass","name":"local","host":"127.0.0.1","port":"9999","type":"start","exe":"C:\\Program Files\\Dyalog\\Dyalog APL-64 16.0 Unicode\\dyalog.exe"},{"ssh_auth_type":"pass","ssh_tnl_auth_type":"pass","name":"p7-61qa","host":"p7-61qa","port":"4503"}]",
"kbdLocale":"en_GB",
"lineNums":"0",
"pfkeys":"["","","{⍺ ⍵} ","FOO ","","","","","","","","",""]",
"selectedExe":"/opt/mdyalog/17.0/64/unicode/mapl",
"title":"{WSID} {PID}",
"wse":"1",
"zoom":"-2"
}

Interpreter:
Version: 16.0.30022
Platform: Windows
Edition: Unicode/32
Date: Jun 2 2017 at 15:00:45

[jayfoad]

This is probably due to the setting of SINGLETRACE on the interpreter side.

[abrudz]

Simple repro:

⎕FX' foo' ' goo'
⎕FX' goo' ' ∘∘∘'
foo

Should look like this (screenshot from Windows RIDE→Linux APL):

[e9gille]

As @jayfoad suggested, this is due to the setting of the SINGLETRACE option of the interpreter.
When starting an interpreter from RIDE, we override any user provided configuration with SINGLETRACE set to 1. This could arguably be changed to allow the user to turn this off.
When connecting to an interpreter started by other means, there's no way for RIDE to dynamically change the setting. The current default in the interpreter is SINGLETRACE=0, which is why you see multiple tabs if connecting to an interpreter started without this explicitly set or set to 0.

[abrudz]

OK, but how does one switch the content of the trace window to higher levels of the stack?

[e9gille]

I was going to say using the Debug window and clicking on the item in the SIStack, but I see that's not working...
I'll need to ask @johndaintree if there's something in the protocol to allow Ride to do that.

[e9gille]

In any case, I committed 828d915 to allow overriding the SINGLETRACE option from RIDE so you can start an interpreter with this turned off.
Switching stack level should be logged as a separate issue.