Path: utzoo!utgpu!water!watmath!clyde!att!pacbell!lll-tis!helios.ee.lbl.gov!pasteur!agate!ig!uwmcsd1!marque!uunet!portal!cup.portal.com!Thomas_E_Zerucha
From: Thomas_E_Zerucha@cup.portal.com
Newsgroups: comp.sys.atari.st
Subject: Re: C compilers on the ST
Message-ID: <6774@cup.portal.com>
Date: 23 Jun 88 00:20:02 GMT
References: <3130@crash.cts.com>
Organization: The Portal System (TM)
Lines: 16
XPortal-User-Id: 1.1001.3273

I don't li
I don't like CSD.  They have a difficult setup for keys, you need to hit
several to do anything.  It also replots the entire screen (fast, but it
still flashes irritatingly) each time you do anything.  On my PC, and even
under PC Ditto, I have used Power C's C-Trace.  For some silly reason, they
chose things like insert to set breakpoints and watchpoints, spacebar to
single step, and return to exectute in trace mode instead of some obscure
set of function keys.  And it highlights successive lines until it actually
goes off screen and can handle graphics.
     I also can't see the assembly instructions, so I had to also use db
separately to trace a problem - I can't see the low level in CSD.  It also
crashed (db too!) when I ran a problem program.  I don't think they did a
bad technical job with CSD - just a bad ergonomic job.  I hope they fix it,
because otherwise it is a good debugger.  The ST's function keys just aren't
the best to overload with functions, and I need both db and csd's functions
in one debugger.\