Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!wuarchive!emory!gatech!prism!sun13!hudgens
From: hudgens@sun13.scri.fsu.edu (Jim Hudgens)
Newsgroups: comp.unix.ultrix
Subject: Re: ds5000/200 Ultrix4 dbx problems
Message-ID: <1179@sun13.scri.fsu.edu>
Date: 19 Oct 90 00:59:24 GMT
References: <26832@cs.yale.edu>
Organization: SCRI, Florida State University
Lines: 32

In article <26832@cs.yale.edu> weier@twolf.ce.yale.edu writes:

   It appears that dbx for the DS5000 provides no way of calling a
   function.  Why has the extremely handy "call" command been removed?
   This drastically cuts into our development efficiency!

We recently complained about this through the proper channels.
The person I spoke to mentioned that he would file a QAR (???) or something
like that.  This cripples dbx for one person here who needs it
for a FORTRAN application which uses fairly complicated data structures
built out of arrays, and needs the ability to call a print routine
which pretty prints the data-structure.

   Another problem
   with this version of dbx is that it does not recognize conditional
   break points when a program is rerun.  The break points show up with
   the status command, but they are ignored.  Deleting break command and
   retyping the same thing over causes it to work.

I noticed several problems with the debugger in this area as well.
If both a tracepoint and a breakpoint are set, only one of them
will have any effect (maybe not true in general, but definitely 
true for the code I was debugging).  This hasn't been reported (yet).

Also, how does one catch an overflow/underflow/divide-by-zero error
under dbx?  Is there a standard way to have a signal delivered 
when a floating point error occurs?  

-- 
Disclaimer:  I didn't do it.
Jim Hudgens		Supercomputer Computations Research Institute
hudgens@sun13.scri.fsu.edu