Studio debugger since 2018.1.1

Debugging, Studio, Caché

Hello,

Last weekend we've updated our Caché version to

Versie:

Cache for Windows (x86-64) 2018.1.1 (Build 312U)

I'm using Studio to develop. I've been using the built-in debugger and it has been working nicely. But now, since the upgrade, I'm getting this error when trying to debug any routine or class method:

Executing ##class(Blue.App.Handler.Adsolut).TestConnection()
<COMMAND>zDebugStub+30^%Debugger.System.1

This is the code for the classmethod I got the error on;

Class Blue.App.Handler.Adsolut Extends %RegisteredObject
{
ClassMethod TestConnection()
{
w "ok"
q
}
}

This is my Studio version information;

Cache' Studio Client 2018.1.1 Build 312
Server Cache for Windows (x86-64) 2018.1.1 (Build 312U)

Does anyone know what's wrong?

Answers

Answer by Eduard Lebedyuk 14 March 2019

Right after you get this error, what's in your ^||isc.debug global?

zw ^||isc.debug

Comment by Rueben Van Mol 14 March 2019

Hello Eduard,

I'm sorry if I misunderstand what you want me to try, but when I run this command from my terminal I get no result at all:

USER>zw ^||isc.debug

USER>

(including the command in the method I'm debugging isn't working either as the cursor never gets "into" the method. It stops somewhere before executing the actual classmethod...)

Comment by Alexey Maslov 16 March 2019

As it is process private global, you should run the command from within the process, in your case from Studio Output pane.

Comment by Rueben Van Mol 18 March 2019

No response there either...

<COMMAND>zDebugStub+30^%Debugger.System.1
Cible de
La cible a quitté le débogueur
zw ^||isc.debug

Comments

Comment by Rueben Van Mol 26 March 2019

Is anyone else experiencing this error? Any ideas where to look next?

Comment by Donna Goodall 27 March 2019

Yes - I just received the same error. I also just recently installed Ensemble 2018.

I have posted to my internal co-workers to see if anyone else has seen the same error. No word back yet.

There was a mention of a new method in the 2016 upgrade checklist, but I had no problems debugging in 2016.

Comment by Jeffrey Drumm 27 March 2019

I've copied your class into my local environment and am not getting any errors using the Studio debugger.

Cache for Windows (x86-64) 2018.1.2 (Build 309U) Mon Mar 4 2019 15:05:44 EST [HealthShare Modules:Core:15.032.9020 + Linkage Engine:15.032.9020]

Class Blue.App.Handler.Absolut Extends %RegisteredObject
{

ClassMethod TestConnection()
{
    w "ok"
    q
}

}

Debugger executing '##class(Blue.App.Handler.Absolut).TestConnection()' Executing ##class(Blue.App.Handler.Absolut).TestConnection() ok Program has terminated. Target has exited debugger

Comment by Vic Sun 27 March 2019

Hello Rueben,

Please review your Caché user permissions. I suspect you may be running into an issue with the secure debug shell as documented here:

https://docs.intersystems.com/latest/csp/docbook/DocBook.UI.Page.cls?KEY=GCAS_secmgmt_secureshell

I hope that is helpful to you but if you are still troubleshooting I would recommend reaching out to the WRC to investigate.

+ 3

Comment by Jeffrey Drumm 27 March 2019

I created a new user with the %Developer role and verified that the class could be debugged successfully. I then added the %SecureBreak role to that user and encountered an issue similar, but not identical to the one reported by @Rueben Van Mol and @Donna Goodall:

<COMMAND>zDebugStub+30^%Debugger.System.1 Invalid debugger target: ##class(Blue.App.Handler.Absolut).TestConnection() Target has exited debugger

+ 1

Comment by Rueben Van Mol 29 March 2019

Yes! Thanks!

this worked for me...

We had to remove the %SecureBreak role from our user (and restart Caché). This did the trick!

Thanks guys!

Regards,

Rueben

Comment by Jeffrey Drumm 30 March 2019

I think you really only needed to log out and back in again; at least that worked for me.