Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!usc!cs.utexas.edu!uunet!news!nujoizey!gwu From: gwu@nujoizey.tcs.com (George Wu) Newsgroups: comp.lang.c++ Subject: Re: RFI: Debugging C++ Keywords: debugging C++ Message-ID: <1948@news.tcs.com> Date: 26 Mar 91 23:28:36 GMT References: Sender: root@tcs.com Reply-To: gwu@nujoizey.tcs.com (George Wu) Distribution: comp Organization: Teknekron Communications Systems Lines: 36 Cc: cimshop!davidm@uunet.UU.NET - I'm not sure which about Comeau's environment, since I've never used it, but in general, debugging C++ code as C++ code is usually provided with C++ to C translators (Cfront). Here're my comments on some of the debuggers I've used so far, all but the last of which is a Cfront based translator: o Sun dbx for C++ 2.0 (dbx++) - Overall, the debugger works. It does get confused in some very annoying ways, ie. it sometimes loses the ability to recognize a variable name; o Saber C++ - I've only ported to Saber, and not developed under it, so I can only volunteer what I know from Saber C: it's simply the most efficient development system (debugger) of which I know; the main drawback is that it eats *HUGE* amounts of memory, both RAM and swap; o HP xdb++ - Again, I'm only just beginning to use HP C++, and I've got alot to learn first, including Softbench; so far it's been easier to use than Sun's dbx++, but not nearly as nice as Saber C++; o GNU gdb - Doesn't fully understand any application using multiple inheritance, but otherwise has set the standard for me concerning non-windows (textual interface) based debuggers; better than dbx, sdb, or any other, but not quite as good as xdb++. That's all I'll say for now. In a month or so, I hope to know more about both Softbench and Saber C++, enough so that I can post unqualified opinions. Until then, I hope this helps. George ---- George J Wu, Software Engineer | gwu@tcs.com or uunet!tcs!gwu Teknekron Communications Systems, Inc.| (415) 649-3752 2121 Allston Way, Berkeley, CA, 94704 | Quit reading news. Get back to work.