Changes between Version 2 and Version 3 of WaveformDeveloperGuide

Timestamp:

02/13/10 21:07:12 (16 years ago)

Author:

ismael (IP: 62.57.1.15)

Comment:

--

WaveformDeveloperGuide

@@ -51 +51 @@
 [[BR]]
 
-== Debugging Waveforms with Eclipse (or gdb) ==
+== Debugging Waveforms ==
 
-Once your ALOE is running, and just after loading the application, you can attach to the running process using your favourite debugger (gdb, ddd, eclipse, etc.). The following steps lead you to debug a waveform component:
+Once your ALOE is running, and just after loading the application, you can attach to the running process using your favourite debugger (gdb, ddd, eclipse, etc.). The following steps explain how to debug a waveform component:
 
-1. Launch ALOE with a positive debug level (this will prevent the components to be killed when stopped by the debugger:
+1. Launch ALOE with the debug option argument. This will prevent the components to be killed when stopped by the debugger:
 
 {{{
@@ -67 +67 @@
 }}}
 
-3. Create or open an Eclipse project for your component.
+3. Open your debugger and attach to the component process. 
 
-4. Place a break-point on every component you want to debug, in the INIT or in the RUN phase
-
-5. Right-click in the binary (left-frame, "Project Explorer") and select debug
-
-6. Select the first item of the left (Attach to Process) and click the ''New'' icon of the icon's menu. Click ''Debug''.
-
-7. Back to the runph prompt, type:
+4. Back to the runph prompt, type:
 
 {{{
@@ -81 +75 @@
 }}}
 
-8. If you placed a breakpoint in the initialization phase, you will see how the program stops on it. You can continue the execution (step by step or free running) until the component arrives to the Status() call. At that point, you can begin to debug the RUN phase. We recommended using  step-by-step execution, so you can place a breakpoint anywhere in the RUN piece of code and you will see how the program stops on every timeslot. In the runph prompt type:
+5. If you placed a breakpoint in the initialization phase, you will see how the program stops on it. You can continue the execution (step by step or free running) until the component arrives to the Status() call. At that point, you can begin to debug the RUN phase. We recommended using  phstep execution, because you can place a breakpoint anywhere in the RUN piece of code and you will see how the program stops on every timeslot. In the runph prompt type:
 
 {{{
@@ -87 +81 @@
 }}}
 
-9. Leave the component in free-run (in Eclipse), it will fall to idle, until the next step, so, go back to runph prompt and type ''phstep'' again. Remember that you also have the option to remove breakpoints and run a finite number of steps, you can do so by typing, in the runph prompt:
+6. Leave the component in free-run, it will fall to idle, until the next step, so, go back to runph prompt and type ''phstep'' again. Remember that you also have the option to remove breakpoints and run a finite number of steps, you can do so by typing, in the runph prompt:
 
 {{{