Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

assert_perror(3) [redhat man page]

ASSERT_PERROR(3)					     Linux Programmer's Manual						  ASSERT_PERROR(3)

NAME
assert_perror - test errnum and abort SYNOPSIS
#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 output and terminates the program by calling abort() 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. CONFORMING TO
This is a GNU extension. BUGS
The purpose of the assert macros is to help the programmer find bugs in his program, 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
exit(3), abort(3), assert(3), strerror(3) GNU
2002-08-25 ASSERT_PERROR(3)

Check Out this Related 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)
Man Page

3 More Discussions You Might Find Interesting

1. HP-UX

USRSTACK macro

I'm upleveling code from 10.20 to 11.11....but I'm running into a problem in which the USRSTACK macro does not seem to be defined in 11.11. Has anybody else experienced this/fixed it/worked around it? Is there a different macro I should be using instead? Thanks for any info you can provide!! (1 Reply)
Discussion started by: jalburger
1 Replies

2. UNIX for Dummies Questions & Answers

compressing code onto one line

hi, i am trying to rewrite some of my code onto one line. but it's not working. what's happening is that the program exits and doesn't execute any of the code that follows. did i make a mistake? i'm guesssing that there is something wrong with my final, "&& exit". or is possible... (1 Reply)
Discussion started by: ankimo
1 Replies

3. Programming

Way to print a code with substituted macro..?

Is there any way to produce a code with all use dmacro to be substituted up to 'ready for compilation' condition? Some macro are build up and it is hard to replace all them up to final code by hand. I need to see the final line after all macro been applied by preprocessor. How that could be... (5 Replies)
Discussion started by: alex_5161
5 Replies