Path: utzoo!utgpu!watmath!uunet!tut.cis.ohio-state.edu!bloom-beacon!oberon!orion.cf.uci.edu!uci-ics!pompe.ics.uci.edu!schmidt
From: schmidt@pompe.ics.uci.edu (Doug Schmidt)
Newsgroups: gnu.gdb.bug
Subject: using gdb
Message-ID: <4189@paris.ics.uci.edu>
Date: 15 Jan 89 02:37:08 GMT
References: <4186@paris.ics.uci.edu>
Sender: news@paris.ics.uci.edu
Reply-To: Doug Schmidt <schmidt@pompe.ics.uci.edu>
Distribution: gnu
Organization: University of California, Irvine - Dept of ICS
Lines: 20

Hi,

   Could someone please tell me if there is any way to emulate the dbx
``trace'' feature with gdb 3.0?  For example, I'd like to print out
some diagnostics (e.g., parameter list, etc.) every time a particular
function is called, and to have the debugger just keep running
automatically after each output.

   Another useful ability would be to have the debugger *stop*
everytime it entered any and every function.  Is this also possible
using the conditional break feature?

   thanks,
   
      Doug Schmidt
--
schmidt@ics.uci.edu (ARPA) |   Per me si va nella citta' dolente.
office: (714) 856-4043     |   Per me si va nell'eterno dolore.
                           |   Per me si va tra la perduta gente.
                           |   Lasciate ogni speranza o voi ch'entrate.