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.55 2003/01/06 06:19:19 tjr 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 Ta Vt "long double"
371 The following length modifier is valid for the
376 .Bl -column ".Sy Modifier" ".Vt wint_t" ".Vt wchar_t *"
377 .It Sy Modifier Ta Cm c Ta Cm s
378 .It Cm l No (ell) Ta Vt wint_t Ta Vt "wchar_t *"
381 A character that specifies the type of conversion to be applied.
384 A field width or precision, or both, may be indicated by
387 or an asterisk followed by one or more decimal digits and a
393 argument supplies the field width or precision.
394 A negative field width is treated as a left adjustment flag followed by a
395 positive field width; a negative precision is treated as though it were
397 If a single format directive mixes positional
399 and non-positional arguments, the results are undefined.
401 The conversion specifiers and their meanings are:
402 .Bl -tag -width ".Cm diouxX"
406 (or appropriate variant) argument is converted to signed decimal
414 or unsigned hexadecimal
423 conversions; the letters
428 The precision, if any, gives the minimum number of digits that must
429 appear; if the converted value requires fewer digits, it is padded on
434 argument is converted to signed decimal, unsigned octal, or unsigned
435 decimal, as if the format had been
440 These conversion characters are deprecated, and will eventually disappear.
444 argument is rounded and converted in the style
446 .Oo \- Oc Ar d Li \&. Ar ddd Li e \\*[Pm] Ar dd
448 where there is one digit before the
449 decimal-point character
450 and the number of digits after it is equal to the precision;
451 if the precision is missing,
452 it is taken as 6; if the precision is
453 zero, no decimal-point character appears.
456 conversion uses the letter
460 to introduce the exponent.
461 The exponent always contains at least two digits; if the value is zero,
465 .Cm a , A , e , E , f , F , g ,
468 conversions, positive and negative infinity are represented as
472 respectively when using the lowercase conversion character, and
476 respectively when using the uppercase conversion character.
477 Similarly, NaN is represented as
479 when using the lowercase conversion, and
481 when using the uppercase conversion.
485 argument is rounded and converted to decimal notation in the style
487 .Oo \- Oc Ar ddd Li \&. Ar ddd ,
489 where the number of digits after the decimal-point character
490 is equal to the precision specification.
491 If the precision is missing, it is taken as 6; if the precision is
492 explicitly zero, no decimal-point character appears.
493 If a decimal point appears, at least one digit appears before it.
497 argument is converted in style
508 The precision specifies the number of significant digits.
509 If the precision is missing, 6 digits are given; if the precision is zero,
513 is used if the exponent from its conversion is less than \-4 or greater than
514 or equal to the precision.
515 Trailing zeros are removed from the fractional part of the result; a
516 decimal point appears only if it is followed by at least one digit.
520 argument is converted to hexadecimal notation in the style
522 .Oo \- Oc Li 0x Ar h Li \&. Ar hhhp Oo \\*[Pm] Oc Ar d ,
524 where the number of digits after the hexadecimal-point character
525 is equal to the precision specification.
526 If the precision is missing, it is taken as enough to exactly
527 represent the floating-point number; if the precision is
528 explicitly zero, no hexadecimal-point character appears.
529 This is an exact conversion of the mantissa+exponent internal
530 floating point representation; the
532 .Oo \- Oc Li 0x Ar h Li \&. Ar hhh
534 portion represents exactly the mantissa; only denormalized
535 mantissas have a zero value to the left of the hexadecimal
539 is a literal character
541 the exponent is preceded by a positive or negative sign
542 and is represented in decimal, using only enough characters
543 to represent the exponent.
546 conversion uses the prefix
554 to represent the hex digits, and the letter
558 to separate the mantissa and exponent.
568 argument is converted to an
569 .Vt "unsigned char" ,
570 and the resulting character is written.
574 (ell) modifier is used, the
576 argument shall be converted to a
578 and the (potentially multi-byte) sequence representing the
579 single wide character is written, including any shift sequences.
580 If a shift sequence is used, the shift state is also restored
581 to the original state after the character.
591 argument is expected to be a pointer to an array of character type (pointer
593 Characters from the array are written up to (but not including)
597 if a precision is specified, no more than the number specified are
599 If a precision is given, no null character
600 need be present; if the precision is not specified, or is greater than
601 the size of the array, the array must contain a terminating
607 (ell) modifier is used, the
609 argument is expected to be a pointer to an array of wide characters
610 (pointer to a wide string).
611 For each wide character in the string, the (potentially multi-byte)
612 sequence representing the
613 wide character is written, including any shift sequences.
614 If any shift sequence is used, the shift state is also restored
615 to the original state after the string.
616 Wide characters from the array are written up to (but not including)
620 if a precision is specified, no more than the number of bytes specified are
621 written (including shift sequences).
622 Partial characters are never written.
623 If a precision is given, no null character
624 need be present; if the precision is not specified, or is greater than
625 the number of bytes required to render the multibyte representation of
626 the string, the array must contain a terminating wide
632 pointer argument is printed in hexadecimal (as if by
637 The number of characters written so far is stored into the
638 integer indicated by the
640 (or variant) pointer argument.
641 No argument is converted.
646 No argument is converted.
647 The complete conversion specification
653 character is defined in the program's locale (category
656 In no case does a non-existent or small field width cause truncation of
657 a numeric field; if the result of a conversion is wider than the field
659 field is expanded to contain the conversion result.
661 To print a date and time in the form
662 .Dq Li "Sunday, July 3, 10:02" ,
667 are pointers to strings:
668 .Bd -literal -offset indent
670 fprintf(stdout, "%s, %s %d, %.2d:%.2d\en",
671 weekday, month, day, hour, min);
675 to five decimal places:
676 .Bd -literal -offset indent
679 fprintf(stdout, "pi = %.5f\en", 4 * atan(1.0));
682 To allocate a 128 byte string and print into it:
683 .Bd -literal -offset indent
687 char *newfmt(const char *fmt, ...)
691 if ((p = malloc(128)) == NULL)
694 (void) vsnprintf(p, 128, fmt, ap);
699 .Sh SECURITY CONSIDERATIONS
704 functions are easily misused in a manner which enables malicious users
705 to arbitrarily change a running program's functionality through
706 a buffer overflow attack.
711 assume an infinitely long string,
712 callers must be careful not to overflow the actual space;
713 this is often hard to assure.
714 For safety, programmers should use the
720 foo(const char *arbitrary_string, const char *and_another)
726 * This first sprintf is bad behavior. Do not use sprintf!
728 sprintf(onstack, "%s, %s", arbitrary_string, and_another);
731 * The following two lines demonstrate better use of
734 snprintf(onstack, sizeof(onstack), "%s, %s", arbitrary_string,
744 family of functions are also easily misused in a manner
745 allowing malicious users to arbitrarily change a running program's
746 functionality by either causing the program
747 to print potentially sensitive data
748 .Dq "left on the stack" ,
749 or causing it to generate a memory fault or bus error
750 by dereferencing an invalid pointer.
753 can be used to write arbitrary data to potentially carefully-selected
755 Programmers are therefore strongly advised to never pass untrusted strings
758 argument, as an attacker can put format specifiers in the string
759 to mangle your stack,
760 leading to a possible security hole.
761 This holds true even if the string was built using a function like
763 as the resulting string may still contain user-supplied conversion specifiers
764 for later interpolation by
767 Always use the proper secure idiom:
769 .Dl "snprintf(buffer, sizeof(buffer), \*q%s\*q, string);"
771 In addition to the errors documented for the
775 family of functions may fail if:
778 An invalid wide character code was encountered.
780 Insufficient storage space is available.
789 .%T "The FreeBSD Security Architecture"
792 .Pa "/usr/share/doc/{to be determined}" . )
794 Subject to the caveats noted in the
809 With the same reservation, the
820 first appeared in the
823 These were implemented by
824 .An Peter Wemm Aq peter@FreeBSD.org
827 but were later replaced with a different implementation
829 .An Todd C. Miller Aq Todd.Miller@courtesan.com
833 The conversion formats
838 are provided only for backward compatibility.
839 The effect of padding the
841 format with zeros (either by the
843 flag or by specifying a precision), and the benign effect (i.e., none)
850 conversions, as well as other
851 nonsensical combinations such as
853 are not standard; such combinations
858 family of functions currently lack the ability to use the
860 flag in conjunction with the
862 conversion specifier.
867 conversion specifiers have not yet been implemented.
870 modifier for floating point formats simply round the
874 providing no additional precision.
878 family of functions do not correctly handle multibyte characters in the