Debbuger is not working?

Posted by pcgroup on 06-Apr-2011 05:49

I have openedge 10.2B The Debugger is not working even I used:

> proDebugEnable -enabel-all

When I choose debug for (start.p) it doesnt stop to step-into my code.

Any Help.

All Replies

Posted by hgarapat on 07-Apr-2011 01:40

There is a typo in your debugger enable command. The command should be as follows

proDebugEnable -enable-all

The above command should be run in Proenv window.

-Harish

Posted by egarcia on 07-Apr-2011 08:26

The Debugger in OpenEdge Architect 10.2B, detects whether debugging is enabled or not and shows the following dialog if it is not enabled.

EnableDebuggerDialog.png


Then Architect switches to the OpenEdge Debugger perspective.

The OpenEdge session then is suspended at the first executable line of the program.

Here are some questions/ideas that you could lead to a solution.

Does the OpenEdge session start?

Does the program run?

Is there a debug session in Debug view in the OpenEdge Debugger perspective?

What happens if you try to run using the launch configuration dialog (selecting the arrow in th Debug button) or using Debug As from the context menu in the editor.

Are there any error messages written to the error log (.log file in the .metadata directory)? (It can be view from Help->About OpenEdge Architect / Configuration Details/View Error Log)

I hope this helps.

Posted by pcgroup on 09-Apr-2011 02:25

Thank you for your reply

- The debugger is enabled

- When I start debug  the procedure start.p from the sampleAppSolution Starts

and it opens the loginDlg form, and the debugger doesn't stop even

I add a breakpoint

- There is no error in the error log.

- I'm using 2003 Server SP1

Thanks

Posted by egarcia on 12-Apr-2011 13:04

I took a look at the screenshot.

I do not know why the Debugger did not stop.

Perhaps, this is one of those issues where Customer Support would take a  look (via WebEx) and identify the source of the problem.

The Debugger should stop at the first executable statement of the program being debugged. In this case "loginDlg = new LogDlg()".

A possible error that you could be getting an error indicating that the debugger segment is not valid. Perhaps, the code was compiled into r-code without debug information.

Are you getting any error message?


Have you re-compiled the project?


When the dialog is showing, can you use the suspend button to give access to the debugger?

You could also add a message statement before and after the display of the dialog to see if the program is doing what you expect.

I hope this helps.

Posted by pcgroup on 20-Apr-2011 06:32

Thanks

The Program is working and the form loginDlg showup with no errors, But the Debugger doesn't stop.

That means the Procedure is sure compiled.

I think it may be a problem with my windows 2003 server.

Thanks to every one tried to help me.

This thread is closed