1 .\" $NetBSD: printf.3,v 1.58 2010/12/26 12:39:54 jnemeth Exp $
3 .\" Copyright (c) 1990, 1991, 1993
4 .\" The Regents of the University of California. All rights reserved.
6 .\" This code is derived from software contributed to Berkeley by
7 .\" Chris Torek and the American National Standards Committee X3,
8 .\" on Information Processing Systems.
10 .\" Redistribution and use in source and binary forms, with or without
11 .\" modification, are permitted provided that the following conditions
13 .\" 1. Redistributions of source code must retain the above copyright
14 .\" notice, this list of conditions and the following disclaimer.
15 .\" 2. Redistributions in binary form must reproduce the above copyright
16 .\" notice, this list of conditions and the following disclaimer in the
17 .\" documentation and/or other materials provided with the distribution.
18 .\" 3. Neither the name of the University nor the names of its contributors
19 .\" may be used to endorse or promote products derived from this software
20 .\" without specific prior written permission.
22 .\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
23 .\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
24 .\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
25 .\" ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
26 .\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
27 .\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
28 .\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
29 .\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
30 .\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
31 .\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
34 .\" @(#)printf.3 8.1 (Berkeley) 6/4/93
53 .Nd formatted output conversion
59 .Fn printf "const char * restrict format" ...
61 .Fn fprintf "FILE * restrict stream" "const char * restrict format" ...
63 .Fn dprintf "int fd" "const char * restrict format" ...
65 .Fn sprintf "char * restrict str" "const char * restrict format" ...
67 .Fn snprintf "char * restrict str" "size_t size" "const char * restrict format" ...
69 .Fn asprintf "char ** restrict ret" "const char * restrict format" ...
72 .Fn vprintf "const char * restrict format" "va_list ap"
74 .Fn vfprintf "FILE * restrict stream" "const char * restrict format" "va_list ap"
76 .Fn vsprintf "char * restrict str" "const char * restrict format" "va_list ap"
78 .Fn vdprintf "int fd" "const char * restrict format" "va_list ap"
80 .Fn vsnprintf "char * restrict str" "size_t size" "const char * restrict format" "va_list ap"
82 .Fn vsnprintf_ss "char * restrict str" "size_t size" "const char * restrict format" "va_list ap"
84 .Fn vasprintf "char ** restrict ret" "const char * restrict format" "va_list ap"
88 family of functions produces output according to a
98 the standard output stream;
102 write output to the given output
107 write output to the give file descriptor
115 write to the character string
121 write to a dynamically allocated string that is stored in
124 These functions write the output under the control of a
126 string that specifies how subsequent arguments
127 (or arguments accessed via the variable-length argument facilities of
129 are converted for output.
132 is a signal-safe standalone version that does not handle
133 floating point formats.
138 return a pointer to a buffer sufficiently large to hold the
142 This pointer should be passed to
144 to release the allocated storage when it is no longer needed.
145 If sufficient space cannot be allocated, these functions
146 will return \-1 and set
151 Please note that these functions are not standardized, and not all
152 implementations can be assumed to set the
157 It is more portable to check for a return value of \-1 instead.
165 of the characters printed into the output string
168 character then gets the terminating
170 if the return value is greater than or equal to the
172 argument, the string was too short
173 and some of the printed characters were discarded.
176 is zero, nothing is written and
185 effectively assume an infinite
188 The format string is composed of zero or more directives:
193 which are copied unchanged to the output stream;
194 and conversion specifications, each of which results
195 in fetching zero or more subsequent arguments.
196 Each conversion specification is introduced by
199 The arguments must correspond properly (after type promotion)
200 with the conversion specifier.
203 the following appear in sequence:
206 An optional field, consisting of a decimal digit string followed by a
208 specifying the next argument to access.
209 If this field is not provided, the argument following the last
210 argument accessed will be used.
211 Arguments are numbered starting at
213 If unaccessed arguments in the format string are interspersed with ones that
214 are accessed the results will be indeterminate.
216 Zero or more of the following flags:
217 .Bl -tag -width ".So \ Sc (space)"
219 The value should be converted to an
230 conversions, this option has no effect.
233 conversions, the precision of the number is increased to force the first
234 character of the output string to a zero (except if a zero value is printed
235 with an explicit precision of zero).
240 conversions, a non-zero result has the string
246 conversions) prepended to it.
257 conversions, the result will always contain a decimal point, even if no
258 digits follow it (normally, a decimal point appears in the results of
259 those conversions only if a digit follows).
264 conversions, trailing zeros are not removed from the result as they
266 .It So Cm 0 Sc (zero)
268 For all conversions except
270 the converted value is padded on the left with zeros rather than blanks.
271 If a precision is given with a numeric conversion
284 A negative field width flag;
285 the converted value is to be left adjusted on the field boundary.
288 conversions, the converted value is padded on the right with blanks,
289 rather than on the left with blanks or zeros.
295 .It So "\ " Sc (space)
296 A blank should be left before a positive number
297 produced by a signed conversion
310 A sign must always be placed before a
311 number produced by a signed conversion.
314 overrides a space if both are used.
320 or the integral portion of a floating point conversion
324 should be grouped and separated by thousands using
325 the non-monetary separator returned by
329 An optional decimal digit string specifying a minimum field width.
330 If the converted value has fewer characters than the field width, it will
331 be padded with spaces on the left (or right, if the left-adjustment
332 flag has been given) to fill out the field width.
334 An optional precision, in the form of a period
336 followed by an optional digit string.
337 If the digit string is omitted, the precision is taken as zero.
338 This gives the minimum number of digits to appear for
346 conversions, the number of digits to appear after the decimal-point for
354 conversions, the maximum number of significant digits for
358 conversions, or the maximum number of characters to be printed from a
363 An optional length modifier, that specifies the size of the argument.
364 The following length modifiers are valid for the
365 .Cm d , i , n , o , u , x ,
369 .Bl -column ".Cm q Em (deprecated)" ".Vt signed char" ".Vt unsigned long long" ".Vt long long *"
370 .It Sy Modifier Ta Cm d , i Ta Cm o , u , x , X Ta Cm n
371 .It Cm hh Ta Vt "signed char" Ta Vt "unsigned char" Ta Vt "signed char *"
372 .It Cm h Ta Vt short Ta Vt "unsigned short" Ta Vt "short *"
373 .It Cm l No (ell) Ta Vt long Ta Vt "unsigned long" Ta Vt "long *"
374 .It Cm ll No (ell ell) Ta Vt "long long" Ta Vt "unsigned long long" Ta Vt "long long *"
375 .It Cm j Ta Vt intmax_t Ta Vt uintmax_t Ta Vt "intmax_t *"
376 .It Cm t Ta Vt ptrdiff_t Ta (see note) Ta Vt "ptrdiff_t *"
377 .It Cm z Ta (see note) Ta Vt size_t Ta (see note)
378 .It Cm q Em (deprecated) Ta Vt quad_t Ta Vt u_quad_t Ta Vt "quad_t *"
384 modifier, when applied to a
388 conversion, indicates that the argument is of an unsigned type
389 equivalent in size to a
393 modifier, when applied to a
397 conversion, indicates that the argument is of a signed type equivalent in
400 Similarly, when applied to an
402 conversion, it indicates that the argument is a pointer to a signed type
403 equivalent in size to a
407 if the standard integer types described in
409 are used, it is recommended that the predefined format string specifier
410 macros are used when possible.
411 These are further described in
414 The following length modifier is valid for the
425 .Bl -column ".Sy Modifier" ".Cm a , A , e , E , f , F , g , G"
426 .It Sy Modifier Ta Cm a , A , e , E , f , F , g , G
427 .It Cm l No (ell) Ta Vt double
428 (ignored, same behavior as without it)
429 .It Cm L Ta Vt "long double"
432 The following length modifier is valid for the
437 .Bl -column ".Sy Modifier" ".Vt wint_t" ".Vt wchar_t *"
438 .It Sy Modifier Ta Cm c Ta Cm s
439 .It Cm l No (ell) Ta Vt wint_t Ta Vt "wchar_t *"
442 A character that specifies the type of conversion to be applied.
445 A field width or precision, or both, may be indicated by
448 or an asterisk followed by one or more decimal digits and a
454 argument supplies the field width or precision.
455 A negative field width is treated as a left adjustment flag followed by a
456 positive field width; a negative precision is treated as though it were
458 If a single format directive mixes positional
460 and non-positional arguments, the results are undefined.
462 The conversion specifiers and their meanings are:
463 .Bl -tag -width ".Cm diouxX"
467 (or appropriate variant) argument is converted to signed decimal
475 or unsigned hexadecimal
484 conversions; the letters
489 The precision, if any, gives the minimum number of digits that must
490 appear; if the converted value requires fewer digits, it is padded on
495 argument is converted to signed decimal, unsigned octal, or unsigned
496 decimal, as if the format had been
502 These conversion characters are deprecated, and will eventually disappear.
506 argument is rounded and converted in the style
508 .Oo \- Oc Ar d Li \&. Ar ddd Li e \*[Pm] Ar dd
510 where there is one digit before the
511 decimal-point character
512 and the number of digits after it is equal to the precision;
513 if the precision is missing,
514 it is taken as 6; if the precision is
515 zero, no decimal-point character appears.
518 conversion uses the letter
522 to introduce the exponent.
523 The exponent always contains at least two digits; if the value is zero,
536 conversions, positive and negative infinity are represented as
540 respectively when using the lowercase conversion character, and
544 respectively when using the uppercase conversion character.
545 Similarly, NaN is represented as
547 when using the lowercase conversion, and
549 when using the uppercase conversion.
553 argument is rounded and converted to decimal notation in the style
555 .Oo \- Oc Ar ddd Li \&. Ar ddd ,
557 where the number of digits after the decimal-point character
558 is equal to the precision specification.
559 If the precision is missing, it is taken as 6; if the precision is
560 explicitly zero, no decimal-point character appears.
561 If a decimal point appears, at least one digit appears before it.
565 argument is converted in style
576 The precision specifies the number of significant digits.
577 If the precision is missing, 6 digits are given; if the precision is zero,
581 is used if the exponent from its conversion is less than \-4 or greater than
582 or equal to the precision.
583 Trailing zeros are removed from the fractional part of the result; a
584 decimal point appears only if it is followed by at least one digit.
588 argument is rounded and converted to hexadecimal notation in the style
590 .Oo \- Oc Li 0x Ar h Li \&. Ar hhhp Oo \*[Pm] Oc Ar d ,
592 where the number of digits after the hexadecimal-point character
593 is equal to the precision specification.
594 If the precision is missing, it is taken as enough to represent
595 the floating-point number exactly, and no rounding occurs.
596 If the precision is zero, no hexadecimal-point character appears.
599 is a literal character
601 and the exponent consists of a positive or negative sign
602 followed by a decimal number representing an exponent of 2.
605 conversion uses the prefix
613 to represent the hex digits, and the letter
617 to separate the mantissa and exponent.
619 Note that there may be multiple valid ways to represent floating-point
620 numbers in this hexadecimal format.
622 .Li 0x3.24p+0 , 0x6.48p-1
626 The format chosen depends on the internal representation of the
627 number, but the implementation guarantees that the length of the
628 mantissa will be minimized.
629 Zeroes are always represented with a mantissa of 0 (preceded by a
631 if appropriate) and an exponent of
642 argument is converted to an
643 .Vt "unsigned char" ,
644 and the resulting character is written.
648 (ell) modifier is used, the
650 argument shall be converted to a
652 and the (potentially multi-byte) sequence representing the
653 single wide character is written, including any shift sequences.
654 If a shift sequence is used, the shift state is also restored
655 to the original state after the character.
665 argument is expected to be a pointer to an array of character type (pointer
667 Characters from the array are written up to (but not including)
671 if a precision is specified, no more than the number specified are
673 If a precision is given, no null character
674 need be present; if the precision is not specified, or is greater than
675 the size of the array, the array must contain a terminating
681 (ell) modifier is used, the
683 argument is expected to be a pointer to an array of wide characters
684 (pointer to a wide string).
685 For each wide character in the string, the (potentially multi-byte)
686 sequence representing the
687 wide character is written, including any shift sequences.
688 If any shift sequence is used, the shift state is also restored
689 to the original state after the string.
690 Wide characters from the array are written up to (but not including)
694 if a precision is specified, no more than the number of bytes specified are
695 written (including shift sequences).
696 Partial characters are never written.
697 If a precision is given, no null character
698 need be present; if the precision is not specified, or is greater than
699 the number of bytes required to render the multibyte representation of
700 the string, the array must contain a terminating wide
706 pointer argument is printed in hexadecimal (as if by
711 The number of characters written so far is stored into the
712 integer indicated by the
714 (or variant) pointer argument.
715 No argument is converted.
720 No argument is converted.
721 The complete conversion specification is
726 character is defined in the program's locale (category
729 In no case does a non-existent or small field width cause truncation of
730 a numeric field; if the result of a conversion is wider than the field
732 field is expanded to contain the conversion result.
734 These functions return
735 the number of characters printed, or that would be printed if there
736 was adequate space in case of
741 (not including the trailing
743 used to end output to strings).
744 If an output error was encountered, these functions shall return a
747 To print a date and time in the form
748 .Dq Li "Sunday, July 3, 10:02" ,
753 are pointers to strings:
754 .Bd -literal -offset indent
755 #include \*[Lt]stdio.h\*[Gt]
756 fprintf(stdout, "%s, %s %d, %.2d:%.2d\en",
757 weekday, month, day, hour, min);
761 to five decimal places:
762 .Bd -literal -offset indent
763 #include \*[Lt]math.h\*[Gt]
764 #include \*[Lt]stdio.h\*[Gt]
765 fprintf(stdout, "pi = %.5f\en", 4 * atan(1.0));
768 To allocate a 128 byte string and print into it:
769 .Bd -literal -offset indent
770 #include \*[Lt]stdio.h\*[Gt]
771 #include \*[Lt]stdlib.h\*[Gt]
772 #include \*[Lt]stdarg.h\*[Gt]
773 char *newfmt(const char *fmt, ...)
777 if ((p = malloc(128)) == NULL)
780 (void) vsnprintf(p, 128, fmt, ap);
786 In addition to the errors documented for the
790 family of functions may fail if:
793 An invalid wide-character code was encountered.
795 Insufficient storage space is available.
805 Subject to the caveats noted in the
820 With the same reservation, the
837 are modeled on the ones that first appeared in the GNU C library.
840 is non-standard and appeared in
855 assume an infinitely long string, callers must be careful not to
856 overflow the actual space; this is often impossible to assure.
857 For safety, programmers should use the
861 family of interfaces instead.
864 interfaces are not available on older
867 interfaces are not yet portable.
869 It is important never to pass a string with user-supplied data as a
872 An attacker can put format specifiers in the string to mangle your stack,
873 leading to a possible security hole.
874 This holds true even if you have built the string
876 using a function like
878 as the resulting string may still contain user-supplied conversion specifiers
879 for later interpolation by
882 Be sure to use the proper secure idiom:
883 .Bd -literal -offset indent
884 snprintf(buffer, sizeof(buffer), "%s", string);
887 There is no way for printf to know the size of each argument passed.
888 If you use positional arguments you must ensure that all parameters, up to the
889 last positionally specified parameter, are used in the format string.
890 This allows for the format string to be parsed for this information.
891 Failure to do this will mean your code is non-portable and liable to fail.
893 In this implementation, passing a
898 format specifier will output
901 Programs that depend on this behavior are non-portable and may crash
902 on other systems or in the future.
904 The conversion formats
909 are not standard and are provided only for backward compatibility.
910 The effect of padding the
912 format with zeros (either by the
914 flag or by specifying a precision), and the benign effect (i.e. none)
921 conversions, as well as other nonsensical combinations such as
923 are not standard; such combinations should be avoided.
927 family of functions do not correctly handle multibyte characters in the
930 .Sh SECURITY CONSIDERATIONS
935 functions are easily misused in a manner which enables malicious users
936 to arbitrarily change a running program's functionality through
937 a buffer overflow attack.
942 assume an infinitely long string,
943 callers must be careful not to overflow the actual space;
944 this is often hard to assure.
945 For safety, programmers should use the
951 foo(const char *arbitrary_string, const char *and_another)
957 * This first sprintf is bad behavior. Do not use sprintf!
959 sprintf(onstack, "%s, %s", arbitrary_string, and_another);
962 * The following two lines demonstrate better use of
965 snprintf(onstack, sizeof(onstack), "%s, %s", arbitrary_string,
975 family of functions are also easily misused in a manner
976 allowing malicious users to arbitrarily change a running program's
977 functionality by either causing the program
978 to print potentially sensitive data
979 .Dq "left on the stack" ,
980 or causing it to generate a memory fault or bus error
981 by dereferencing an invalid pointer.
984 can be used to write arbitrary data to potentially carefully-selected
986 Programmers are therefore strongly advised to never pass untrusted strings
989 argument, as an attacker can put format specifiers in the string
990 to mangle your stack,
991 leading to a possible security hole.
992 This holds true even if the string was built using a function like
994 as the resulting string may still contain user-supplied conversion specifiers
995 for later interpolation by
998 Always use the proper secure idiom:
1000 .Dl "snprintf(buffer, sizeof(buffer), \*q%s\*q, string);"