1 .\" Copyright (c) 1990, 1991, 1993
2 .\" The Regents of the University of California. All rights reserved.
4 .\" This code is derived from software contributed to Berkeley by
5 .\" Chris Torek and the American National Standards Committee X3,
6 .\" on Information Processing Systems.
8 .\" Redistribution and use in source and binary forms, with or without
9 .\" modification, are permitted provided that the following conditions
11 .\" 1. Redistributions of source code must retain the above copyright
12 .\" notice, this list of conditions and the following disclaimer.
13 .\" 2. Redistributions in binary form must reproduce the above copyright
14 .\" notice, this list of conditions and the following disclaimer in the
15 .\" documentation and/or other materials provided with the distribution.
16 .\" 3. All advertising materials mentioning features or use of this software
17 .\" must display the following acknowledgement:
18 .\" This product includes software developed by the University of
19 .\" California, Berkeley and its contributors.
20 .\" 4. Neither the name of the University nor the names of its contributors
21 .\" may be used to endorse or promote products derived from this software
22 .\" without specific prior written permission.
24 .\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
25 .\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
26 .\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
27 .\" ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
28 .\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
29 .\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
30 .\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
31 .\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
32 .\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
33 .\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
36 .\" @(#)printf.3 8.1 (Berkeley) 6/4/93
37 .\" $FreeBSD: src/lib/libc/stdio/printf.3,v 1.58 2004/10/16 16:00:01 stefanf Exp $
43 .Nm printf , fprintf , sprintf , snprintf , asprintf ,
44 .Nm vprintf , vfprintf, vsprintf , vsnprintf , vasprintf
45 .Nd formatted output conversion
51 .Fn printf "const char * restrict format" ...
53 .Fn fprintf "FILE * restrict stream" "const char * restrict format" ...
55 .Fn sprintf "char * restrict str" "const char * restrict format" ...
57 .Fn snprintf "char * restrict str" "size_t size" "const char * restrict format" ...
59 .Fn asprintf "char **ret" "const char *format" ...
62 .Fn vprintf "const char * restrict format" "va_list ap"
64 .Fn vfprintf "FILE * restrict stream" "const char * restrict format" "va_list ap"
66 .Fn vsprintf "char * restrict str" "const char * restrict format" "va_list ap"
68 .Fn vsnprintf "char * restrict str" "size_t size" "const char * restrict format" "va_list ap"
70 .Fn vasprintf "char **ret" "const char *format" "va_list ap"
74 family of functions produces output according to a
84 the standard output stream;
88 write output to the given output
95 write to the character string
101 dynamically allocate a new string with
104 These functions write the output under the control of a
106 string that specifies how subsequent arguments
107 (or arguments accessed via the variable-length argument facilities of
109 are converted for output.
111 These functions return the number of characters printed
112 (not including the trailing
114 used to end output to strings) or a negative value if an output error occurs,
119 which return the number of characters that would have been printed if the
122 (again, not including the final
132 to be a pointer to a buffer sufficiently large to hold the formatted string.
133 This pointer should be passed to
135 to release the allocated storage when it is no longer needed.
136 If sufficient space cannot be allocated,
140 will return \-1 and set
153 of the characters printed into the output string
156 character then gets the terminating
158 if the return value is greater than or equal to the
160 argument, the string was too short
161 and some of the printed characters were discarded.
162 The output is always null-terminated.
169 effectively assume an infinite
172 The format string is composed of zero or more directives:
177 which are copied unchanged to the output stream;
178 and conversion specifications, each of which results
179 in fetching zero or more subsequent arguments.
180 Each conversion specification is introduced by
184 The arguments must correspond properly (after type promotion)
185 with the conversion specifier.
188 the following appear in sequence:
191 An optional field, consisting of a decimal digit string followed by a
193 specifying the next argument to access.
194 If this field is not provided, the argument following the last
195 argument accessed will be used.
196 Arguments are numbered starting at
198 If unaccessed arguments in the format string are interspersed with ones that
199 are accessed the results will be indeterminate.
201 Zero or more of the following flags:
202 .Bl -tag -width ".So \ Sc (space)"
204 The value should be converted to an
207 .Cm c , d , i , n , p , s ,
210 conversions, this option has no effect.
213 conversions, the precision of the number is increased to force the first
214 character of the output string to a zero (except if a zero value is printed
215 with an explicit precision of zero).
220 conversions, a non-zero result has the string
226 conversions) prepended to it.
228 .Cm a , A , e , E , f , F , g ,
231 conversions, the result will always contain a decimal point, even if no
232 digits follow it (normally, a decimal point appears in the results of
233 those conversions only if a digit follows).
238 conversions, trailing zeros are not removed from the result as they
240 .It So Cm 0 Sc (zero)
242 For all conversions except
244 the converted value is padded on the left with zeros rather than blanks.
245 If a precision is given with a numeric conversion
246 .Cm ( d , i , o , u , i , x ,
253 A negative field width flag;
254 the converted value is to be left adjusted on the field boundary.
257 conversions, the converted value is padded on the right with blanks,
258 rather than on the left with blanks or zeros.
264 .It So "\ " Sc (space)
265 A blank should be left before a positive number
266 produced by a signed conversion
267 .Cm ( a , A , d , e , E , f , F , g , G ,
271 A sign must always be placed before a
272 number produced by a signed conversion.
275 overrides a space if both are used.
281 or the integral portion of a floating point conversion
285 should be grouped and separated by thousands using
286 the non-monetary separator returned by
290 An optional decimal digit string specifying a minimum field width.
291 If the converted value has fewer characters than the field width, it will
292 be padded with spaces on the left (or right, if the left-adjustment
293 flag has been given) to fill out
296 An optional precision, in the form of a period
299 optional digit string.
300 If the digit string is omitted, the precision is taken as zero.
301 This gives the minimum number of digits to appear for
302 .Cm d , i , o , u , x ,
305 conversions, the number of digits to appear after the decimal-point for
306 .Cm a , A , e , E , f ,
309 conversions, the maximum number of significant digits for
313 conversions, or the maximum number of characters to be printed from a
318 An optional length modifier, that specifies the size of the argument.
319 The following length modifiers are valid for the
320 .Cm d , i , n , o , u , x ,
324 .Bl -column ".Cm q Em (deprecated)" ".Vt signed char" ".Vt unsigned long long" ".Vt long long *"
325 .It Sy Modifier Ta Cm d , i Ta Cm o , u , x , X Ta Cm n
326 .It Cm hh Ta Vt "signed char" Ta Vt "unsigned char" Ta Vt "signed char *"
327 .It Cm h Ta Vt short Ta Vt "unsigned short" Ta Vt "short *"
328 .It Cm l No (ell) Ta Vt long Ta Vt "unsigned long" Ta Vt "long *"
329 .It Cm ll No (ell ell) Ta Vt "long long" Ta Vt "unsigned long long" Ta Vt "long long *"
330 .It Cm j Ta Vt intmax_t Ta Vt uintmax_t Ta Vt "intmax_t *"
331 .It Cm t Ta Vt ptrdiff_t Ta (see note) Ta Vt "ptrdiff_t *"
332 .It Cm z Ta (see note) Ta Vt size_t Ta (see note)
333 .It Cm q Em (deprecated) Ta Vt quad_t Ta Vt u_quad_t Ta Vt "quad_t *"
339 modifier, when applied to a
343 conversion, indicates that the argument is of an unsigned type
344 equivalent in size to a
348 modifier, when applied to a
352 conversion, indicates that the argument is of a signed type equivalent in
355 Similarly, when applied to an
357 conversion, it indicates that the argument is a pointer to a signed type
358 equivalent in size to a
361 The following length modifier is valid for the
362 .Cm a , A , e , E , f , F , g ,
366 .Bl -column ".Sy Modifier" ".Cm a , A , e , E , f , F , g , G"
367 .It Sy Modifier Ta Cm a , A , e , E , f , F , g , G
368 .It Cm l No (ell) Ta Vt double
369 (ignored, same behavior as without it)
370 .It Cm L Ta Vt "long double"
373 The following length modifier is valid for the
378 .Bl -column ".Sy Modifier" ".Vt wint_t" ".Vt wchar_t *"
379 .It Sy Modifier Ta Cm c Ta Cm s
380 .It Cm l No (ell) Ta Vt wint_t Ta Vt "wchar_t *"
383 A character that specifies the type of conversion to be applied.
386 A field width or precision, or both, may be indicated by
389 or an asterisk followed by one or more decimal digits and a
395 argument supplies the field width or precision.
396 A negative field width is treated as a left adjustment flag followed by a
397 positive field width; a negative precision is treated as though it were
399 If a single format directive mixes positional
401 and non-positional arguments, the results are undefined.
403 The conversion specifiers and their meanings are:
404 .Bl -tag -width ".Cm diouxX"
408 (or appropriate variant) argument is converted to signed decimal
416 or unsigned hexadecimal
425 conversions; the letters
430 The precision, if any, gives the minimum number of digits that must
431 appear; if the converted value requires fewer digits, it is padded on
436 argument is converted to signed decimal, unsigned octal, or unsigned
437 decimal, as if the format had been
442 These conversion characters are deprecated, and will eventually disappear.
446 argument is rounded and converted in the style
448 .Oo \- Oc Ar d Li \&. Ar ddd Li e \\*[Pm] Ar dd
450 where there is one digit before the
451 decimal-point character
452 and the number of digits after it is equal to the precision;
453 if the precision is missing,
454 it is taken as 6; if the precision is
455 zero, no decimal-point character appears.
458 conversion uses the letter
462 to introduce the exponent.
463 The exponent always contains at least two digits; if the value is zero,
467 .Cm a , A , e , E , f , F , g ,
470 conversions, positive and negative infinity are represented as
474 respectively when using the lowercase conversion character, and
478 respectively when using the uppercase conversion character.
479 Similarly, NaN is represented as
481 when using the lowercase conversion, and
483 when using the uppercase conversion.
487 argument is rounded and converted to decimal notation in the style
489 .Oo \- Oc Ar ddd Li \&. Ar ddd ,
491 where the number of digits after the decimal-point character
492 is equal to the precision specification.
493 If the precision is missing, it is taken as 6; if the precision is
494 explicitly zero, no decimal-point character appears.
495 If a decimal point appears, at least one digit appears before it.
499 argument is converted in style
510 The precision specifies the number of significant digits.
511 If the precision is missing, 6 digits are given; if the precision is zero,
515 is used if the exponent from its conversion is less than \-4 or greater than
516 or equal to the precision.
517 Trailing zeros are removed from the fractional part of the result; a
518 decimal point appears only if it is followed by at least one digit.
522 argument is rounded and converted to hexadecimal notation in the style
524 .Oo \- Oc Li 0x Ar h Li \&. Ar hhhp Oo \\*[Pm] Oc Ar d ,
526 where the number of digits after the hexadecimal-point character
527 is equal to the precision specification.
528 If the precision is missing, it is taken as enough to represent
529 the floating-point number exactly, and no rounding occurs.
530 If the precision is zero, no hexadecimal-point character appears.
533 is a literal character
535 and the exponent consists of a positive or negative sign
536 followed by a decimal number representing an exponent of 2.
539 conversion uses the prefix
547 to represent the hex digits, and the letter
551 to separate the mantissa and exponent.
553 Note that there may be multiple valid ways to represent floating-point
554 numbers in this hexadecimal format.
556 .Li 0x3.24p+0 , 0x6.48p-1
560 The format chosen depends on the internal representation of the
561 number, but the implementation guarantees that the length of the
562 mantissa will be minimized.
563 Zeroes are always represented with a mantissa of 0 (preceded by a
565 if appropriate) and an exponent of
576 argument is converted to an
577 .Vt "unsigned char" ,
578 and the resulting character is written.
582 (ell) modifier is used, the
584 argument shall be converted to a
586 and the (potentially multi-byte) sequence representing the
587 single wide character is written, including any shift sequences.
588 If a shift sequence is used, the shift state is also restored
589 to the original state after the character.
599 argument is expected to be a pointer to an array of character type (pointer
601 Characters from the array are written up to (but not including)
605 if a precision is specified, no more than the number specified are
607 If a precision is given, no null character
608 need be present; if the precision is not specified, or is greater than
609 the size of the array, the array must contain a terminating
615 (ell) modifier is used, the
617 argument is expected to be a pointer to an array of wide characters
618 (pointer to a wide string).
619 For each wide character in the string, the (potentially multi-byte)
620 sequence representing the
621 wide character is written, including any shift sequences.
622 If any shift sequence is used, the shift state is also restored
623 to the original state after the string.
624 Wide characters from the array are written up to (but not including)
628 if a precision is specified, no more than the number of bytes specified are
629 written (including shift sequences).
630 Partial characters are never written.
631 If a precision is given, no null character
632 need be present; if the precision is not specified, or is greater than
633 the number of bytes required to render the multibyte representation of
634 the string, the array must contain a terminating wide
640 pointer argument is printed in hexadecimal (as if by
645 The number of characters written so far is stored into the
646 integer indicated by the
648 (or variant) pointer argument.
649 No argument is converted.
654 No argument is converted.
655 The complete conversion specification
661 character is defined in the program's locale (category
664 In no case does a non-existent or small field width cause truncation of
665 a numeric field; if the result of a conversion is wider than the field
667 field is expanded to contain the conversion result.
669 To print a date and time in the form
670 .Dq Li "Sunday, July 3, 10:02" ,
675 are pointers to strings:
676 .Bd -literal -offset indent
678 fprintf(stdout, "%s, %s %d, %.2d:%.2d\en",
679 weekday, month, day, hour, min);
683 to five decimal places:
684 .Bd -literal -offset indent
687 fprintf(stdout, "pi = %.5f\en", 4 * atan(1.0));
690 To allocate a 128 byte string and print into it:
691 .Bd -literal -offset indent
695 char *newfmt(const char *fmt, ...)
699 if ((p = malloc(128)) == NULL)
702 (void) vsnprintf(p, 128, fmt, ap);
707 .Sh SECURITY CONSIDERATIONS
712 functions are easily misused in a manner which enables malicious users
713 to arbitrarily change a running program's functionality through
714 a buffer overflow attack.
719 assume an infinitely long string,
720 callers must be careful not to overflow the actual space;
721 this is often hard to assure.
722 For safety, programmers should use the
728 foo(const char *arbitrary_string, const char *and_another)
734 * This first sprintf is bad behavior. Do not use sprintf!
736 sprintf(onstack, "%s, %s", arbitrary_string, and_another);
739 * The following two lines demonstrate better use of
742 snprintf(onstack, sizeof(onstack), "%s, %s", arbitrary_string,
752 family of functions are also easily misused in a manner
753 allowing malicious users to arbitrarily change a running program's
754 functionality by either causing the program
755 to print potentially sensitive data
756 .Dq "left on the stack" ,
757 or causing it to generate a memory fault or bus error
758 by dereferencing an invalid pointer.
761 can be used to write arbitrary data to potentially carefully-selected
763 Programmers are therefore strongly advised to never pass untrusted strings
766 argument, as an attacker can put format specifiers in the string
767 to mangle your stack,
768 leading to a possible security hole.
769 This holds true even if the string was built using a function like
771 as the resulting string may still contain user-supplied conversion specifiers
772 for later interpolation by
775 Always use the proper secure idiom:
777 .Dl "snprintf(buffer, sizeof(buffer), \*q%s\*q, string);"
779 In addition to the errors documented for the
783 family of functions may fail if:
786 An invalid wide character code was encountered.
788 Insufficient storage space is available.
797 .%T "The FreeBSD Security Architecture"
800 .Pa "/usr/share/doc/{to be determined}" . )
802 Subject to the caveats noted in the
817 With the same reservation, the
828 first appeared in the
831 These were implemented by
832 .An Peter Wemm Aq peter@FreeBSD.org
835 but were later replaced with a different implementation
837 .An Todd C. Miller Aq Todd.Miller@courtesan.com
841 The conversion formats
846 are provided only for backward compatibility.
847 The effect of padding the
849 format with zeros (either by the
851 flag or by specifying a precision), and the benign effect (i.e., none)
858 conversions, as well as other
859 nonsensical combinations such as
861 are not standard; such combinations
866 family of functions do not correctly handle multibyte characters in the