Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!gatech!hao!husc6!mit-eddie!genrad!decvax!ucbvax!CORY.BERKELEY.EDU!dillon
From: dillon@CORY.BERKELEY.EDU (Matt Dillon)
Newsgroups: comp.sys.amiga
Subject: Re: Task Spawning Difficulties
Message-ID: <8706191424.AA20196@cory.Berkeley.EDU>
Date: Fri, 19-Jun-87 10:24:50 EDT
Article-I.D.: cory.8706191424.AA20196
Posted: Fri Jun 19 10:24:50 1987
Date-Received: Mon, 22-Jun-87 02:33:03 EDT
Sender: daemon@ucbvax.BERKELEY.EDU
Lines: 11



	Yup, that would do it.  The reason DB had problems single-stepping
through the AddTask() is obvious... AddTask() probably does a Forbid() for
several very good reasons, but when tracing, any Forbid()'s are effectively
NOP's (since the tracer task must run also).  I've found that putting the
thing in trace mode (bt) usually works better than tracing (t/T).  And,
of course, you can open another window (aN) and do a wait in it (aL) to
catch the created task.

				-Ml:ca