Bug 88052 - register_printf_function() forgets to clear table
Summary: register_printf_function() forgets to clear table
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: glibc
Version: 9
Hardware: i686
OS: Linux
Target Milestone: ---
Assignee: Jakub Jelinek
QA Contact: Brian Brock
Depends On:
TreeView+ depends on / blocked
Reported: 2003-04-04 22:01 UTC by John Reiser
Modified: 2016-11-24 14:53 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2003-04-09 19:21:37 UTC

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2003:136 0 high SHIPPED_LIVE glibc bugfix errata 2003-04-09 04:00:00 UTC
Red Hat Product Errata RHSA-2003:089 0 high SHIPPED_LIVE : Updated glibc packages fix vulnerabilities in RPC XDR decoder 2003-04-10 04:00:00 UTC

Description John Reiser 2003-04-04 22:01:43 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.0) Gecko/20020529

Description of problem:
Routine register_printf_function() in stdio-common/reg-printf.c forgets to clear
the table when allocating it, before inserting the first translation function. 
The table is consulted for all format characters, not just those that use the
registered arginfo or functions.  So if malloc() happens to return a block that
was used before, then parse_one_spec() will go wrong if the consulted slot has
non-zero garbage.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. Run testcase stdio-common/tst-printfsz.
2. Watch as parse_one_spec() examines the entry for 'g' which has not been

Actual Results:  __printf_arginfo_table['g'] and __printf_function_table['g']
are used even though they have not been initialized.  In the usual case,
malloc() without any preceding free() happens to return zeroed memory [as if

Expected Results:  _printf_arginfo_table and __printf_function_table should be
initialized before use.

Additional info:

Fix: s/malloc/calloc/ in stdio-common/reg-printf.c line 49.

This could have been detected by running valgrind (or any other uninit memory
detector) when running the glibc testcases.

Comment 1 Jakub Jelinek 2003-04-09 19:21:37 UTC
An errata has been issued which should help the problem described in this bug report. 
This report is therefore being closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files, please follow the link below. You may reopen 
this bug report if the solution does not work for you.


Note You need to log in before you can comment on or make changes to this bug.