Path: utzoo!attcan!uunet!cs.utexas.edu!usc!apple!agate!ucbvax!SCRI1.SCRI.FSU.EDU!"VAXINO::DAVID"
From: "VAXINO::DAVID"@SCRI1.SCRI.FSU.EDU
Newsgroups: comp.sys.sgi
Subject: problems with dbx
Message-ID: <890801161738.20220b2f@SCRI1.SCRI.FSU.EDU>
Date: 1 Aug 89 20:17:38 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The Internet
Lines: 32

I am using dbx and edge to debug some rather large fortran programs (~20k 
lines) on a 3130. I have been able to get dbx to die several times with the
following error: 

       dbx: internal error: skimsource: too many lines

This error has occurred with both the List command and when the debugger 
attempts to display the source code of a break point. 

I have also been able to get the debugger to die in such a way that it 
actually HANGS the machine! This error normally occurs while the debugger
is loading in the symbolic information but before it prints "(dbx)". 

These errors both seem to go away when I run my code through egrep just 
before compilation to remove of the comment lines (code size ~10k lines).

A third error that I have come across is not being able to print out the 
contents of arrays that are passed in to a subroutine. The error is some 
gibberish about null pointers. The only way that I have found around this 
error is to reference the variables from the calling procedure. For 
example:
               print main.var1[1]

- David LaSalle
  SCRI
  Florida State University
  Tallahassee, FL  32306-4052
  (904)644-8532

arpanet: minuit@scri1.scri.fsu.edu  (128.186.4.1)
         or
         minuit%fsu@nmfecc.arpa