home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!spool.mu.edu!uwm.edu!psuvax1!rutgers!cbmvax!cbmehq!cbmfra!forgeas
- From: forgeas@swinjm.adsp.sub.org (Jean-Michel Forgeas)
- Newsgroups: comp.sys.amiga.programmer
- Subject: Re: InputHandler debugging (long)
- Message-ID: <ZEEds*ua2@swinjm.adsp.sub.org>
- Date: 31 Dec 92 10:19:41 GMT
- References: <tomme.724365078@Minsk> <lk1stgINNsej@exodus.Eng.Sun.COM>
- Reply-To: forgeas@swinjm.adsp.sub.org (Jean-Michel Forgeas)
- Organization: The Software Winery
- Lines: 18
- X-Newsreader: Arn V1.00 alpha rel2
-
- In article <lk1stgINNsej@exodus.Eng.Sun.COM>, Chuck McManis writes:
-
- > The best way to debug any sort of task (input handlers included) is
- > to "create" a debug port.
-
- An easy way is to use kprintf() (link with debug.lib from Commodore)
- which acts like printf().
- To have the prints to appear on a console, you have to start "Sushi"
- first (a very useful tool from Commodore too). If you don't start
- "Sushi" the prints go to the serial port.
- You can use kprintf() from a task.
-
- Best regards,
- Jean-Michel
- --
- Jean-Michel Forgeas uunet!cbmvax!cbmehq!cbmfra!swinjm!forgeas
- 16170 Bordeville __
- France \/
-