Debugging in Studio

[Michoel Reach]

I have been using the Studio debugger for quite some time with good results. But in a new Cache' system we are setting up now, I'm running into an issue I haven't seen before: If I start debugging from a tag in the routine (right-click, Set ___ as debug target) and then begin stepping through the code, I get the blue mark on the left and the text highlighted, as usual. But if the code continues into a different routine, and I Step Into it w F11, very often I can't see where it is in the new routine. The routine opens in Studio, it seems to be stepping through the code with each F10 or F11, but the display never leaves the top line of the new routine. I can't tell where I am, and obviously can't find out much in debugging.

Is this a well-known issue, and what can I do about it?

Thanks

Michael Reach

[Joel Solon]

This usually happens when the routine A calls routine B, but there’s only OBJ code for routine B (no INT/MAC for routine B). You’ll usually see a popup about “no source code” or something.

If what you’re seeing is that A calls B, and the source for B actually loads, yet the debugger isn’t advancing command by command through B, I’d try re-compiling B and debugging again.

You didn’t say which version of Caché you’re using, and what version of Caché Studio you’re using.

--
--
Caché, Ensemble, DeepSee

---
You received this message because you are subscribed to the Google Groups "Caché, Ensemble, DeepSee" group.
To unsubscribe from this group and stop receiving emails from it, send an email to intersystems-publi...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Michoel Reach]

The source for B did actually load. But I tried recompiling B and now it works properly. Not sure why that helped, but thanks! I'll come back if I run into the problem further.

Michael

[OldMster]

Intersystems seems to be using some hidden index to check for the existence of source code some of the time.  I have occurrences where I go to edit a routine, pull it from the list in Studio, then it tells me the routine doesn't exist.  Recompiling the routine usually solves the problem.

Mark

[Mack]

Depending on the access you are granted, I have found it best to recompile all routines when upgrading/moving. I preface the "access" portion because there are some companies who fail to provide the INT/MAC routines, which you have to be careful to ensure you don't cause issues and add costs for them to repair. I like to refer to it as the "old school developer" mentality.