Skip to main content

Call Stack

  • July 17, 2014
  • 5 replies
  • 0 views

We are in the process of moving over from MFE to Enterprise Developer for Eclipse

While in Debug mode, how can I see the previous stack entries within the same program?

I see one entry defining the current line of execution. Other entries, one per program, shows the line that were last executed, normally the call to the next program.

Within MFE, we can see within the current program, the call stack for the paragraphs leading up to the current execution point. So we can put a breakpoint in the general abort paragraph, and just run to there. Checking the call stack, its easy to see how the program got there.   


#EnterpriseDeveloper

5 replies

Chris Glazier
Forum|alt.badge.img+2
  • Moderator
  • 3695 replies
  • July 17, 2014

We are in the process of moving over from MFE to Enterprise Developer for Eclipse

While in Debug mode, how can I see the previous stack entries within the same program?

I see one entry defining the current line of execution. Other entries, one per program, shows the line that were last executed, normally the call to the next program.

Within MFE, we can see within the current program, the call stack for the paragraphs leading up to the current execution point. So we can put a breakpoint in the general abort paragraph, and just run to there. Checking the call stack, its easy to see how the program got there.   


#EnterpriseDeveloper

The Call Stack should be shown within the Debug window and it should include performed paragraphs up to the current execution point.
If you click on a previous paragraph name in the call stack it will show you the source statement that brought you there.

Example: my program has paragraph 000-begin which performs 110-new-para.
Below is what shows in the call stack in the debug view window.


  • Author
  • Rocketeer
  • 19312 replies
  • July 24, 2014

We are in the process of moving over from MFE to Enterprise Developer for Eclipse

While in Debug mode, how can I see the previous stack entries within the same program?

I see one entry defining the current line of execution. Other entries, one per program, shows the line that were last executed, normally the call to the next program.

Within MFE, we can see within the current program, the call stack for the paragraphs leading up to the current execution point. So we can put a breakpoint in the general abort paragraph, and just run to there. Checking the call stack, its easy to see how the program got there.   


#EnterpriseDeveloper

No, not working as described.

I'm in the second paragrap[h of the subprogram. I see the call point from the main program to the submodule. And I see the current execution point. I do not see the point in the first paragraph of the sub program, neither is the first program main paragrapgh displayed.

 

 

Wish I could add a screenprint, but the insert/edit Media option does not work either.

Webpage error details

User Agent: Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 6.1; Trident/4.0; SLCC2; .NET CLR 2.0.50727; .NET CLR 3.5.30729; .NET CLR 3.0.30729; Media Center PC 6.0; .NET CLR 1.1.4322; .NET4.0C; .NET4.0E; InfoPath.3)
Timestamp: Thu, 24 Jul 2014 09:55:23 UTC


Message: Expected '('
Line: 98
Char: 7
Code: 0
URI: http://community.microfocus.com/tiny_mce/plugins/insertmedia/js/media.js

 

 


  • Author
  • Rocketeer
  • 19312 replies
  • July 24, 2014

We are in the process of moving over from MFE to Enterprise Developer for Eclipse

While in Debug mode, how can I see the previous stack entries within the same program?

I see one entry defining the current line of execution. Other entries, one per program, shows the line that were last executed, normally the call to the next program.

Within MFE, we can see within the current program, the call stack for the paragraphs leading up to the current execution point. So we can put a breakpoint in the general abort paragraph, and just run to there. Checking the call stack, its easy to see how the program got there.   


#EnterpriseDeveloper

No, not working as described.

I'm in the second paragrap[h of the subprogram. I see the call point from the main program to the submodule. And I see the current execution point. I do not see the point in the first paragraph of the sub program, neither is the first program main paragrapgh displayed.

 

 

Wish I could add a screenprint, but the insert/edit Media option does not work either.

Webpage error details

User Agent: Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 6.1; Trident/4.0; SLCC2; .NET CLR 2.0.50727; .NET CLR 3.5.30729; .NET CLR 3.0.30729; Media Center PC 6.0; .NET CLR 1.1.4322; .NET4.0C; .NET4.0E; InfoPath.3)
Timestamp: Thu, 24 Jul 2014 09:55:23 UTC


Message: Expected '('
Line: 98
Char: 7
Code: 0
URI: http://community.microfocus.com/tiny_mce/plugins/insertmedia/js/media.js

 

 


  • Author
  • Rocketeer
  • 19312 replies
  • July 24, 2014

We are in the process of moving over from MFE to Enterprise Developer for Eclipse

While in Debug mode, how can I see the previous stack entries within the same program?

I see one entry defining the current line of execution. Other entries, one per program, shows the line that were last executed, normally the call to the next program.

Within MFE, we can see within the current program, the call stack for the paragraphs leading up to the current execution point. So we can put a breakpoint in the general abort paragraph, and just run to there. Checking the call stack, its easy to see how the program got there.   


#EnterpriseDeveloper

under Options, add file does work.


Chris Glazier
Forum|alt.badge.img+2
  • Moderator
  • 3695 replies
  • July 24, 2014

We are in the process of moving over from MFE to Enterprise Developer for Eclipse

While in Debug mode, how can I see the previous stack entries within the same program?

I see one entry defining the current line of execution. Other entries, one per program, shows the line that were last executed, normally the call to the next program.

Within MFE, we can see within the current program, the call stack for the paragraphs leading up to the current execution point. So we can put a breakpoint in the general abort paragraph, and just run to there. Checking the call stack, its easy to see how the program got there.   


#EnterpriseDeveloper

Sorry, I didn't catch that this is Enterprise Developer and you are debugging under Enterprise Server as you have posted this to the Visual COBOL forum.

I will move your post to the Enterprise Developer forum so that the correct engineers can take a look.

Thanks.