Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!decwrl!ucbvax!agate!shelby!neon!neon!gumby From: gumby@Cygnus.COM (David Vinayak Wallace) Newsgroups: comp.sys.next Subject: Debuggers for NeXT (plus lint) Message-ID: Date: 12 Jul 90 02:42:03 GMT References: <1990Jul11.165302.4186@dept.csci.unt.edu> Sender: news@Neon.Stanford.EDU (USENET News System) Organization: Cygnus Support Lines: 29 In-Reply-To: doug@dept.csci.unt.edu's message of 11 Jul 90 16:53:02 GMT Date: 11 Jul 90 16:53:02 GMT From: doug@dept.csci.unt.edu (Douglas Scott) Other than the bundled gdb, are there any other debuggers available for C code? Things such as lint (is there a glint??). I *sorely* miss lint! Have you tried the -Wall option to the C compiler? No, it ain't lint, but it enables warning on almost anything that might trip you up. And, umm, you know, the compiler is free software...YOU could adapt the front end to be an ansi lint... How about something like dbx -- gdb is ok, but not nearly as clever IMHO as dbx... I'm curious -- what's missing? IMAO gdb is more clever; most likely we're each missing out on the strengths of the other's fave debugger. It looks like the upcoming version of gdb will have a dbx front-end. However the NeXT gdb is pretty far out of the mainstream (understandably -- they had to add all the mach support `n stuff) so I doubt it would drop in easily. If I remember, the version NeXT forked off with predates the hairy command processing. C'mon, a graphics-based machine with no graphics debugger? Really!