For review: forward_move always moves

Erwan Jahier Erwan.Jahier at irisa.fr
Fri Jul 17 22:36:20 AEST 1998


This is for Fergus.

I do this change because it is the way forward_move should behave
according to Mireille Opium's specification.


runtime/mercury_trace_external.c:
	Start to find a forward matching event from the next event rather
	from the current event (e.g., now forward_move(nop, nop, ..., nop)
	moves one event forward).

Index: mercury_trace_external.c
===================================================================
RCS file:
/home/mercury1/repository/mercury/runtime/mercury_trace_external.c,v
retrieving revision 1.3
diff -u -r1.3 mercury_trace_external.c
--- mercury_trace_external.c	1998/07/13 22:44:12	1.3
+++ mercury_trace_external.c	1998/07/17 09:55:28
@@ -303,16 +323,16 @@
 }
 
 void
MR_trace_event_external(const MR_Stack_Layout_Label *layout,
	MR_trace_port port, Unsigned seqno, Unsigned depth, const char *path)
 {
 	static bool searching = FALSE;
 	static Word search_data;
 	Word debugger_request;
	Integer debugger_request_type;
	Word var_list;
 
-do_search:
 	if (searching) {
 		/* XXX should also pass registers here,
 		   since they're needed for checking for matches with the
@@ -343,20 +363,55 @@
 				}
 				search_data = debugger_request;
 			        searching = TRUE;
-				goto do_search;

-- 
R1.



More information about the developers mailing list