Interfacing the Debugger - Revision history

Jfiat at 07:23, 7 May 2007

2007-05-07T07:23:32Z

2007-04-11T10:14:24Z

2007-01-21T15:34:10Z

‎Switching between executing and communicating

2007-01-21T15:33:12Z

‎==

2007-01-21T15:32:42Z

‎Inspecting the C stack

2007-01-21T13:20:30Z

‎Requirements on the runtime

2007-01-21T13:01:40Z

‎Requirements on the runtime

2007-01-21T12:56:12Z

‎Introduction

2007-01-20T15:43:46Z

‎Introduction

2007-01-20T14:21:03Z

‎Introduction

@@ Line 1: / Line 1: @@
 [[Category:Compiler]]
-{{Warning|'''Warning''': Article under development}}
+{{UnderConstruction}}
 ====Introduction====

← Older revision		Revision as of 15:34, 21 January 2007
Line 67:		Line 67:
	====Inspecting the C stack====		====Inspecting the C stack====
	====Switching between executing and communicating====		====Switching between executing and communicating====
		+	In the code example above there are several calls to the macro RTHOOK and RTNHOOK.

@@ Line 66: / Line 66: @@
 |}
 ====Inspecting the C stack====
-====
+====Switching between executing and communicating====

@@ Line 15: / Line 15: @@
 The runtime thus needs to be able to inspect the C stack and make the transition between the two states executing and communicating.
+====An Example====
 {|border="0" cellpadding="2" cellspacing="0" align="center"
 |-valign="top" -halign="center"
+|
-<c>
+<eiffel>foo (list: LIST [LIST [ANY]]
-/* foo */
+     str: STRING): BOOLEAN
+   local
 EIF_BOOLEAN Fadkw7f (EIF_REFERENCE Current,
                       EIF_REFERENCE arg1,
@@ Line 53: / Line 62: @@
     return Result;
 }</c>
-−
 </c>
+|
 |}

← Older revision		Revision as of 13:01, 21 January 2007
Line 12:		Line 12:
	* Resume the execution.		* Resume the execution.
	* Give information about variables on the stack or heap.		* Give information about variables on the stack or heap.
−	* ...
−

		+	The runtime thus needs to be able to inspect the C stack and make the transition between the two states executing and communicating.

@@ Line 3: / Line 3: @@
 ====Introduction====
-EiffelStudio supports a rich debugging feature set for workbench code. When a
+EiffelStudio supports a rich debugging feature set for workbench code. Finalized systems can only be debugged at the C level.
 {|border="0" cellpadding="2" cellspacing="0" align="center"

@@ Line 18: / Line 18: @@
     EIF_BOOLEAN Result = (EIF_BOOLEAN) 0;
     ...
     RTLU (SK_BOOL, &Result);
     RTLU(SK_REF,&arg1);
     RTLU(SK_REF,&arg2);
@@ Line 24: / Line 26: @@
     RTLU(SK_INT32, &loc1);
     ...
-    RTHOOK(1);
+    RTHOOK(1);  //Signal debugger, breakpoint slot 1 reached
     loc1 = (EIF_INTEGER_32)((EIF_INTEGER_32) 10L);
-    RTHOOK(2);
+    RTHOOK(2);  //Signal debugger, breakpoint slot 2 reached
     tp1 = (FUNCTION_CAST(EIF_REFERENCE, (EIF_REFERENCE))
        RTVF(100, 33, "first", arg1))(arg1);
-    RTNHOOK(2);
+    RTNHOOK(2); //Signal debugger, nested breakpoint slot
     tp2 = RTCCL(arg2);
     (FUNCTION_CAST(void, (EIF_REFERENCE, EIF_REFERENCE))
        RTVF(100, 39, "force", tp1))(tp1, tp2);
-    RTHOOK(3);
+    RTHOOK(3);  //Signal debugger, breakpoint slot 3 reached
     Result = (EIF_BOOLEAN)(EIF_BOOLEAN) 1;
-    RTHOOK(4);
+    RTHOOK(4);  //Signal debugger, breakpoint slot 4 reached
-    RTLO(5);
+    RTLO(5);    //Pop the five locals from the debuggers stack
     return Result;