Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!shadooby!samsung!usc!venera.isi.edu!gremlin!gregsun.nrtc.northrop.com!johnson From: johnson@gregsun.nrtc.northrop.com (Greg Johnson ) Newsgroups: comp.lang.c++ Subject: 2.0 C++ <--> DBX ??? Message-ID: <4305@gremlin.nrtc.northrop.com> Date: 15 Nov 89 00:53:39 GMT Sender: news@gremlin.nrtc.northrop.com Reply-To: johnson@gregsun.nrtc.northrop.com (Greg Johnson ) Organization: Northrop Research & Technology Center, Palos Verdes, CA Lines: 22 Is it possible to get ATT C++ 2.0 and dbx to behave together rationally? Any help would be greatly appreciated. I am working on a Sun SPARCstation. If I compile with the `-g' option, dbx (dbxtool, actually) allows me to single-step through programs basically correctly. It does not seem to single-step through implicitly invoked constructors on entry to functions, but I can live with that. The thing that drives me crazy is that dbx does not understand C++ variable names. A colleague things that the `demangler' c++filt might help somehow; but it appears that c++filt has as its purpose in life to make error messages from the loader intelligible. Can c++filt or some other tool make the debugger behave rationally in regard to variable names? I suppose it is possible to specify an option to c++filt to get it to print out a table of ugly native C names and their corresponding C++ source names, and then I could cut and paste a C name into the debugger to make queries of variable values. Sigh. Is there a better way of doing things? Thanks in advance - Greg Johnson ps - I don't usually monitor this group, so please send responses to me (johnson@nrtc.northrop.com).