Path: utzoo!utgpu!news-server.csri.toronto.edu!mailrus!wuarchive!cs.utexas.edu!yale!cmcl2!kramden.acf.nyu.edu!brnstnd
From: brnstnd@kramden.acf.nyu.edu (Dan Bernstein)
Newsgroups: comp.lang.c
Subject: Re: assertions and debuggers
Message-ID: <18373:Sep2203:32:0790@kramden.acf.nyu.edu>
Date: 22 Sep 90 03:32:07 GMT
References: <10835@rama.UUCP> <14186:Sep2105:48:2290@kramden.acf.nyu.edu> <18100@haddock.ima.isc.com>
Distribution: usa
Organization: IR
Lines: 21

In article <18100@haddock.ima.isc.com> karl@haddock.ima.isc.com (Karl Heuer) writes:
> In article <14186:Sep2105:48:2290@kramden.acf.nyu.edu> brnstnd@kramden.acf.nyu.edu (Dan Bernstein) writes:
> >In article <10835@rama.UUCP> lvw@rama.UUCP (Lyndon VanWagner) writes:
> > > On the VAX, we have been able to redefine the assert macro to place
> > > us into the VMS debugger at the point of error, rather than just 
> > > exiting the program.
> >   [ and in UNIX? ]
> > Why not just change the exit() to an abort()?
    [ followed by an explanation (deleted) of how to answer the question ]
> It already *is* an abort().

No, it is not, on this Sun 4 at least. You should be scolded for not
paying attention to portability. ( :-) )

> If you run the program from the debugger, it will
> stop when it gets the SIGABRT.

It may not be worth using the debugger all the time, even when you're
developing the program.

---Dan