exit() will run functions installed with atexit(), and destructors for
C++ static objects, and so on. abort() will kill the program quickly
rather than calling these functions while the program is already in a
bad state (just like a failing assert()).
OK, FWIW (not much :-), I'll change the "ex
On Wed, Dec 30, 2009 at 2:40 PM, Ross Finlayson wrote:
>> Without this patch my VLC exists, pretending everything went fine.
>
> And why do you feel that "abort()" is better than
> "exit()"? (Because you can catch it in a signal handler?)
Because exit(0) means program exited without issue. You
On Wed, 2009-12-30 at 05:40 -0800, Ross Finlayson wrote:
> >Without this patch my VLC exists, pretending everything went fine.
>
> As I noted in my earlier response (to someone else's question), this
> call (and other calls) to "exit()" should be getting called only if
> there's a serious proble
Without this patch my VLC exists, pretending everything went fine.
As I noted in my earlier response (to someone else's question), this
call (and other calls) to "exit()" should be getting called only if
there's a serious problem in your code. Are you actually seeing
this? If so, you should
Hi,
Without this patch my VLC exists, pretending everything went fine.
Pierre.
exit_to_err.diff
Description: Binary data
___
live-devel mailing list
live-devel@lists.live555.com
http://lists.live555.com/mailman/listinfo/live-devel
