Breakpoint in Module Explorer tab

How can I debug modules in Module Explorer tab, which was not exported to OS fromat? Breakpoint doesn't work

Find more posts tagged with

Comments

By Trial and error what I have observed is sometimes the Oscript debugging window will not launch so I will keep "open" that perspective.Sometimes if there are huge .mdmp files in your <OTHOME> the builder and server seems to run but very flakily.in the screencap I have put a break into webdsp:Dispatch and I can see the break point ina side window

You are supposed to send the mdmp files if you observe them to OT so they can better make the product.Screencaps form my eclipse if they help you somewhat.

Version: Luna Service Release 1 (4.4.1 that is running com.opentext.cside_10.5.4.235.jar

A usual check I do is to amke sure the modules are actually loaded by their color

https://knowledge.opentext.com/knowledge/cs.dll?func=ll&objId=59942956&objAction=download

Darcy_Casselman

Pretty much as you'd expect: Open up a script and set a breakpoint.

If this isn't working, please let us know.

Darcy.

HFCDev

I'm getting the exact same problem. I just installed CS 10.5 SP 2 U 2015-03 and its CSIDE plug-in to Eclipse Luna on SQL Server 2012 running on WIndows 7x64. Appu's observation seems to be what is going on, the debug perspective isn't opening. It is however halting execution at my breakpoint, I just don't have a way to proceed. If you release a fix for this, please post that here as well as your usual spots.

-Hugh Ferguson

HFCDev

I can officially confirm Appu's observation. If you set a breakpoint in CSIDE and you don't get the debugger perspective but the code halts (i.e. your request hangs) as would be expected, simply manually change to Debug perspective and it should work from there. If it's not hitting the break-point, I can't help with that

One other weird behaviour was at one point, it was giving me errors in the debugger when attempting to set the breakpoint on a locked ospace. I can understand the BP's not saving but they should be settable anywhere in Content Server. After I restarted, I ceased to get that behaviour, so this time it's a one-off, so not worthy of its own post but I thought I'd mention it.

-Hugh

Olivier_De_Pooter

It seems to me you checked the 'Don't show again' checkbox in the prompt to open debug perspective when hitting a breakpoint, and clicked no. Maybe select a new workspace and recreate your oscript project will do the trick?

Darcy_Casselman

That would be my theory as well, although we have had reports that the Debug perspective very occasionally fails to appear when you hit a breakpoint.

We've enabled the Debug toolbar items in the OScript perspective to give you some visual clue that you're in debug mode. Even if you're not in the editor with a debug context, you can see the Step and Resume buttons lit up, which may server as a cue to switch to the Debug perspective for more details.

The CSIDE plug-in doesn't bring up the perspective itself. We simply implement Eclipse's debug interfaces and it deals with that. That said, as it's now come up a few times, we'll take some time and look into it.

Darcy.

Donna Nalls

Dear All,

I am experiencing this same issue in a brand new CS 20.2 install with both eClipse 2020-03 and 2021-03. I have tried all of the tips above and still no luck. I simply cannot get the debugger to open on a breakpoint! 😣😫

Is anyone currently using CSIDE with CS 20.2? Any issues?

Any thoughts or tips would be greatly appreciated!

Thanks, in advance!!!

Donna

Appu Nair

@dnalls

what if you were to code scheduler.debugbreak() in any of the OS files and have the debugger perspective open. Many times what I have noticed is when you are in eclipse and there are errors in something else the blue compiling visual is a dud.It never works unless all the projects are rid of errors.

Donna Nalls

Thanks, very much, Appu. John Simon made the same suggestion. So, I am able to use scheduler.debugbreak() in my code and the debugger opens. However, still not able to simply add a breakpoint. This gets me moving forward.

Thank You!!!!!

Appu Nair

@dnalls

Not sure if this is a red herring but in our Azure environment I am a domain user with Administrator privileges but somehow eclipse and oclipse don’t seem to obey that so to save any Oscript I always start my session as ‘Run As Administrator’ . I also keep my eclipse projects closed because sometimes I use the same box to do Oscript or Java .

Donna Nalls

Thank you, again. Donovan Smith suggested Run As Administrator, as well. Alas, it did not work. Donovan also reviewed my other configuration settings and everything looked in synch with his. Very perplexing and many hours of my time wasted on this! :( Thanks, Appu -- keep those tips/tricks coming! :)