NetBSD/lib/libc/gen/err.3

169 lines
4.9 KiB
Groff
Raw Normal View History

.\" $NetBSD: err.3,v 1.15 2002/07/10 14:37:12 yamt Exp $
.\"
.\" Copyright (c) 1993
.\" The Regents of the University of California. All rights reserved.
1993-05-01 03:08:23 +04:00
.\"
.\" Redistribution and use in source and binary forms, with or without
.\" modification, are permitted provided that the following conditions
.\" are met:
.\" 1. Redistributions of source code must retain the above copyright
.\" notice, this list of conditions and the following disclaimer.
.\" 2. Redistributions in binary form must reproduce the above copyright
.\" notice, this list of conditions and the following disclaimer in the
.\" documentation and/or other materials provided with the distribution.
.\" 3. All advertising materials mentioning features or use of this software
.\" must display the following acknowledgement:
.\" This product includes software developed by the University of
.\" California, Berkeley and its contributors.
.\" 4. Neither the name of the University nor the names of its contributors
.\" may be used to endorse or promote products derived from this software
.\" without specific prior written permission.
.\"
.\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
.\" ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
.\" SUCH DAMAGE.
.\"
.\" @(#)err.3 8.1 (Berkeley) 6/9/93
1993-05-01 03:08:23 +04:00
.\"
.Dd March 21, 2001
1993-05-01 03:08:23 +04:00
.Dt ERR 3
.Os
1993-05-01 03:08:23 +04:00
.Sh NAME
.Nm err ,
.Nm verr ,
.Nm errx ,
.Nm verrx ,
.Nm warn ,
.Nm vwarn ,
.Nm warnx ,
.Nm vwarnx
.Nd formatted error messages
1998-02-05 21:45:17 +03:00
.Sh LIBRARY
.Lb libc
1993-05-01 03:08:23 +04:00
.Sh SYNOPSIS
2002-02-07 10:00:09 +03:00
.Fd #include \*[Lt]err.h\*[Gt]
1993-05-01 03:08:23 +04:00
.Ft void
.Fn err "int status" "const char *fmt" "..."
1993-05-01 03:08:23 +04:00
.Ft void
.Fn verr "int status" "const char *fmt" "va_list args"
1993-05-01 03:08:23 +04:00
.Ft void
.Fn errx "int status" "const char *fmt" "..."
1993-05-01 03:08:23 +04:00
.Ft void
.Fn verrx "int status" "const char *fmt" "va_list args"
1993-05-01 03:08:23 +04:00
.Ft void
.Fn warn "const char *fmt" "..."
.Ft void
.Fn vwarn "const char *fmt" "va_list args"
.Ft void
.Fn warnx "const char *fmt" "..."
.Ft void
.Fn vwarnx "const char *fmt" "va_list args"
.Sh DESCRIPTION
The
.Fn err
and
.Fn warn
family of functions display a formatted error message on the standard
error output.
In all cases, the last component of the program name, a colon character,
and a space are output.
If the
.Fa fmt
argument is not NULL, the formatted error message is output.
1993-05-01 03:08:23 +04:00
In the case of the
.Fn err ,
.Fn verr ,
.Fn warn ,
and
.Fn vwarn
functions, the error message string affiliated with the current value of
the global variable
2001-09-16 06:30:23 +04:00
.Va errno
is output next, preceded by a colon character and a space if
.Fa fmt
is not NULL.
1993-05-01 03:08:23 +04:00
In all cases, the output is followed by a newline character.
.Pp
The
.Fn err ,
.Fn verr ,
.Fn errx ,
and
.Fn verrx
functions do not return, but instead cause the program to terminate
with the status value given by the argument
.Fa status .
It is often appropriate to use the value
.Dv EXIT_FAILURE ,
defined in
.Aq Ar stdlib.h ,
as the
.Fa status
argument given to these functions.
1993-05-01 03:08:23 +04:00
.Sh EXAMPLES
Display the current
.Va errno
information string and terminate with status indicating failure:
1993-05-01 03:08:23 +04:00
.Bd -literal -offset indent
if ((p = malloc(size)) == NULL)
err(EXIT_FAILURE, NULL);
1993-05-01 03:08:23 +04:00
if ((fd = open(file_name, O_RDONLY, 0)) == -1)
err(EXIT_FAILURE, "%s", file_name);
1993-05-01 03:08:23 +04:00
.Ed
.Pp
Display an error message and terminate with status indicating failure:
1993-05-01 03:08:23 +04:00
.Bd -literal -offset indent
2002-02-07 10:00:09 +03:00
if (tm.tm_hour \*[Lt] START_TIME)
errx(EXIT_FAILURE, "too early, wait until %s",
start_time_string);
1993-05-01 03:08:23 +04:00
.Ed
.Pp
Warn of an error:
.Bd -literal -offset indent
if ((fd = open(raw_device, O_RDONLY, 0)) == -1)
warnx("%s: %s: trying the block device",
raw_device, strerror(errno));
if ((fd = open(block_device, O_RDONLY, 0)) == -1)
warn("%s", block_device);
1993-05-01 03:08:23 +04:00
.Ed
.Sh SEE ALSO
.Xr exit 3 ,
2001-02-20 01:20:15 +03:00
.Xr getprogname 3 ,
1993-05-01 03:08:23 +04:00
.Xr strerror 3
.Sh HISTORY
The
.Fn err
and
.Fn warn
2001-09-16 06:30:23 +04:00
functions first appeared in
1993-11-25 05:48:32 +03:00
.Bx 4.4 .
.Sh CAVEATS
It is important never to pass a string with user-supplied data as a
format without using
.Ql %s .
An attacker can put format specifiers in the string to mangle your stack,
leading to a possible security hole.
This holds true even if you have built the string
.Dq by hand
using a function like
.Fn snprintf ,
as the resulting string may still contain user-supplied conversion specifiers
for later interpolation by the
.Fn err
and
.Fn warn
functions.
.Pp
Always be sure to use the proper secure idiom:
.Bd -literal -offset indent
err(1, "%s", string);
.Ed