Re: use of assert() and exit()

David C Niemi <[email protected]> Mon, 25 Nov 2002 10:44:19 -0500 (EST)
Newsgroups gmane.network.beep.beepcore.c.general
Message-ID <Pine.LNX.4.44.0211251037580.18082-100000@harappa.oldtrail.reston.va.us>
Are failed ASSERT calls and exit() situations coming up in your system?  
If so I'd expect some debugging should be done prior to using it
seriously.

Normally ASSERT and exit would be used in situations where continuing on
would make no sense or possibly be dangerous -- they are "this shouldn't
happen" types of internal errors.  I would expect they should be extremely
rare in real life; and they definitely shouldn't be occurring for normal,
expected sorts of errors like bad data or network-level problems.

DCN

On Mon, 25 Nov 2002, Andy Walshe wrote:
> Hello,
> We use beepcore-c as just one communication module in our system.
> It is a multi-threaded Solaris 8 based system. One thing we have
> noticed is the use of assert() and exit() in the beepcore library.
> We'd prefer to have control when errors occur so as not to stop
> our whole system.
> 
> We can redefine the ASSERT directive to do nothing but the use
> of exit() is a different story. Has anyone had fixes/issues with
> these?
> 
> Thanks
> Andy
> 
> 
> -------------------------------------------------------
> This sf.net email is sponsored by:ThinkGeek
> Welcome to geek heaven.
> http://thinkgeek.com/sf
> _______________________________________________
> Beepcore-c-users mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/beepcore-c-users
> 

-- 
-------------------------------------------------------
-- David C. Niemi           Adeptech Systems, Inc.   --
-- Reston, Virginia, USA    http://www.adeptech.com/ --
-------------------------------------------------------



-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf