Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Posting-Version: version B 2.10.2 (Tek) 9/28/84 based on 9/17/84; site tekcae.UUCP Path: utzoo!watmath!clyde!cbosgd!ihnp4!mhuxn!mhuxj!mhuxr!ulysses!allegra!mit-eddie!genrad!decvax!tektronix!tekcrl!tekcae!daleh From: daleh@tekcae.UUCP (Dale Henrichs) Newsgroups: net.lang.f77 Subject: Re: How Do You Debug Your F77 Programs? Message-ID: <124@tekcae.UUCP> Date: Tue, 15-Jan-85 01:26:13 EST Article-I.D.: tekcae.124 Posted: Tue Jan 15 01:26:13 1985 Date-Received: Wed, 16-Jan-85 21:27:49 EST References: <168@mplvax.UUCP> Reply-To: daleh@tekcae.UUCP (Dale Henrichs) Organization: Tektronix, Beaverton OR Lines: 28 Summary: In article <168@mplvax.UUCP> john@mplvax.UUCP (John McInerney) writes: >My question is, >how do you debug your f77 programs? Do you use a modified version of >sdb? a fixed version of dbx? print statements? After limping along for several months using adb and print statements (I also found dbx to be entirely worthless for f77), I tried to make sdb work again. Not surprisingly, there is nothing wrong with sdb. The 4.2 f77 compiler doesn't put out the correct (from the point of view of sdb) symbol table information, so after a few relatively minor changes to the f77 compiler, sdb was working as it had under 4.1. Also, I made some changes to sdb so that it actually understands f77 (I added complex and double complex data types and more importantly made it possible for sdb to access common block variables, local variables and arrays). If you're interested in any of these enhancements, send me mail and I'll ship you the diffs. Dale Henrichs P.S.: The f77 compiler is being used on ~50K lines of code so the compiler is pretty well debugged. As far as sdb is concerned, it sure is nice to have an f77 debugger, even though it is a little buggy.