[Coldstuff] vm_task bug?

[Allen Noe]

This is a multi-part message in MIME format.
--------------60463A364E678E6688F2ACF6
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Well, I've done some more experiments and found that whatever the second method
called by the driver is, it's going to have a TID of 1, just like startup. So, I
guess it's not really much of a bug, just change the initial value of
next_task_id to 2.

I was thinking that maybe vm_task would be running methods with the TID of the
last method to run, but that doesn't appear to be the case.
--------------60463A364E678E6688F2ACF6
Content-Type: text/plain; charset=us-ascii;
 name="next_task_id.patch"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline;
 filename="next_task_id.patch"

--- Genesis-1.1.10-STABLE/src/execute.c	Thu Mar 28 12:36:30 2002
+++ Genesis-1.1.10-STABLE/src/execute.c.new	Thu Mar 28 12:42:44 2002
@@ -34,7 +34,7 @@
 Int stack_pos, stack_size;
 Int *arg_starts, arg_pos, arg_size;
 Long task_id=1;
-Long next_task_id=1;
+Long next_task_id=2;
 Long call_environ=1;
 Long tick;
 

--------------60463A364E678E6688F2ACF6--