Debugg a .p code

in app builder click on tools->procedure editor
then open ur .p file in that and click compile->debug and you should be able to debug the code via that. you havent given us much to go on what version of progress have you got? and do you mean using the debugger or have you got an actual error message?
 
Greetings,
That is rather ambiguous.
You need to define UR requirements exactly.
To debug a Progress .p is very simple, first U need to be competent in the 4GL, understanding the concepts. Then U need to be competent with program logic. Once U understand the concepts of the programming language. U R able to debug simply. U also failed to mention the Progress version
you are using. E.g. CHAR / GUI / WEBspeed / OpenEdge.
Before anybody is able to assist with UR problem, need to know what page we are on.
BFN
 
Debugg a .p code - facing a problem

Thanks and this was helpful.

I was able to launch the debugger in attachable mode from Windows.

I tried the same with unix by starting the debugger.

I have this following appear in my screen. Does this mean, the debugger has started?

16019 proDebugger
OpenEdge Release 10.0B as of Thu Aug 5 21:54:23 EDT 2004

You must set the DISPLAY variable before running the Debugger.

:confused::confused::confused::confused::confused::confused::confused::confused::confused:

Then I tried to debug command my procedure from the editor. I got a exception like java exception.

Eception in thread "main" java.lang.InternalError: Can't connect to X11 window server using ':0.0' as the value of the DISPLAY variable.

Can you please help me understand this.
 
I dont think you can run the debugger in a terminal window. You need to start an x-window session before it will run, or export your display using something like xming. I've had no problems with the debugger using a VNC session.
 
I've never used progress debugger.

So my degug method is:
message var-names view-as alert-box. // for interacrtive modules

Option SESSION:DEBUG-ALERT=true.
at the begining of program is good to identify line + stack trace when errors occurs.

and for appserver and background processes:

define stream teststream.
output to stream teststream 1.txt append
put stream teststream unformatted STRING (TODAY, "99/99/9999") STRING(TIME, "HH:MM:SS") var-names skip.
for each temp-table-name:
display temp-table-name.
end.
output stream teststream close.
 
for example:

┌───────────────────────────── Error ──────────────────────────────┐
│ ** Unable to open file: setReflectionCaption.rba. Errno=2. (98) │
│ ──────────────────────────────────────────────────────────────── │
│ <OK> <Help> │
└──────────────────────────────────────────────────────────────────┘
<Help> button will be added to any alert-dialog.

┌────────────────────── Stack Trace ───────────────────────┐
│ │
│ ┌────────────────────────────────────────────────────┐ │
│ │ src/system/connect.p (src/system/connect.p) at l│ │
│ │ src/system/usermain.p (src/system/usermain.p) at│ │
│ │ src/system/main.w (src/system/main.w) at line 11│ │
┌───│ │ USER-INTERFACE-TRIGGER src/system/main.w (src/sy│ │───┐
│ **│ │ src/system/testmenu.w (src/system/testmenu.w) at│ │8) │
│ ──│ │ WindowInfo src/system/testmenu.w (src/system/tes│ │── │
│ │ │--> src/system/setReflectCaption.p (src/system/setRe│ │ │
 
You must log in or register to reply here.
Back
Top