assert_perror(3) [x11r4 man page]
ASSERT_PERROR(3) Linux Programmer's Manual ASSERT_PERROR(3) NAME
assert_perror - test errnum and abort SYNOPSIS
#define _GNU_SOURCE /* See feature_test_macros(7) */ #include <assert.h> void assert_perror(int errnum); DESCRIPTION
If the macro NDEBUG was defined at the moment <assert.h> was last included, the macro assert_perror() generates no code, and hence does nothing at all. Otherwise, the macro assert_perror() prints an error message to standard error and terminates the program by calling abort(3) if errnum is nonzero. The message contains the filename, function name and line number of the macro call, and the output of str- error(errnum). RETURN VALUE
No value is returned. ATTRIBUTES
For an explanation of the terms used in this section, see attributes(7). +----------------+---------------+---------+ |Interface | Attribute | Value | +----------------+---------------+---------+ |assert_perror() | Thread safety | MT-Safe | +----------------+---------------+---------+ CONFORMING TO
This is a GNU extension. BUGS
The purpose of the assert macros is to help programmers find bugs in their programs, things that cannot happen unless there was a coding mistake. However, with system or library calls the situation is rather different, and error returns can happen, and will happen, and should be tested for. Not by an assert, where the test goes away when NDEBUG is defined, but by proper error handling code. Never use this macro. SEE ALSO
abort(3), assert(3), exit(3), strerror(3) COLOPHON
This page is part of release 4.15 of the Linux man-pages project. A description of the project, information about reporting bugs, and the latest version of this page, can be found at https://www.kernel.org/doc/man-pages/. GNU 2017-09-15 ASSERT_PERROR(3)
Check Out this Related Man Page
ABORT(3) Linux Programmer's Manual ABORT(3) NAME
abort - cause abnormal process termination SYNOPSIS
#include <stdlib.h> void abort(void); DESCRIPTION
The abort() first unblocks the SIGABRT signal, and then raises that signal for the calling process (as though raise(3) was called). This results in the abnormal termination of the process unless the SIGABRT signal is caught and the signal handler does not return (see longjmp(3)). If the SIGABRT signal is ignored, or caught by a handler that returns, the abort() function will still terminate the process. It does this by restoring the default disposition for SIGABRT and then raising the signal for a second time. RETURN VALUE
The abort() function never returns. ATTRIBUTES
For an explanation of the terms used in this section, see attributes(7). +----------+---------------+---------+ |Interface | Attribute | Value | +----------+---------------+---------+ |abort() | Thread safety | MT-Safe | +----------+---------------+---------+ NOTES
Up until glibc 2.26, if the abort() function caused process termination, all open streams were closed and flushed (as with fclose(3)). However, in some cases this could result in deadlocks and data corruption. Therefore, starting with glibc 2.27, abort() terminates the process without flushing streams. POSIX.1 permits either possible behavior, saying that abort() "may include an attempt to effect fclose() on all open streams". CONFORMING TO
SVr4, POSIX.1-2001, POSIX.1-2008, 4.3BSD, C89, C99. SEE ALSO
gdb(1), sigaction(2), assert(3), exit(3), longjmp(3), raise(3) COLOPHON
This page is part of release 4.15 of the Linux man-pages project. A description of the project, information about reporting bugs, and the latest version of this page, can be found at https://www.kernel.org/doc/man-pages/. GNU
2017-11-26 ABORT(3)