superbol-studio-oss icon indicating copy to clipboard operation
superbol-studio-oss copied to clipboard

Debugging nestcall

Open proteomis opened this issue 1 year ago • 2 comments

Hello, it does not seem possible to debug inside nested programs

For example, in the following program, if you put breakpoints inside "myentry1" or "myentry2", the program is executed but the breakpoints are never reached. ` $set sourceformat"free" identification division. program-id. test-calls.

   procedure division.
   call "myentry1"
   display "Retour d'entry 1"
   call "myentry2"
   display "Retour d'entry 2"
   goback.

   program-id. myentry1.
   procedure division.
   display "Appel de myentry1"
   goback.
   end program myentry1.

   program-id. myentry2.
   procedure division.
   display "Appel de myentry2"
   goback.
   end program myentry2.

   end program test-calls.

*>**`

The only possibilty left to debug inside "myentry1" or "myentry2" is to create new source files "myentry1.cbl" or "myentry2.cbl", suppress the source code from the original source file and paste them in the new source files.

Regards.

proteomis avatar Jun 09 '24 09:06 proteomis

Please:

  • set a breakpoint in test-calls before the first call
  • enable debugging output in the launch config ("verbose": true)
  • start
  • enable a breakpoint in the nested function
  • use the debugging console with info break
  • share the output of the debugging console

GitMensch avatar Jun 10 '24 07:06 GitMensch

@nberth Should get the debugger label.

GitMensch avatar Jan 08 '25 08:01 GitMensch