Prior to this update gawk interpreted (under certain circumstances) some
run-time variables as internal zero-length variable prototypes. When gawk tried
to free such run-time variables, it actually freed the internal prototypes, that
were allocated just once due to memory savings. Consequently gawk sometimes
failed and the error message "awk: double free or corruption" was displayed.
With this update the problem has been corrected and the error no longer occurs.

Technical note added. If any revisions are required, please edit the "Technical Notes" field
accordingly. All revisions will be proofread by the Engineering Content Services team.
New Contents:
Prior to this update gawk interpreted (under certain circumstances) some
run-time variables as internal zero-length variable prototypes. When gawk tried
to free such run-time variables, it actually freed the internal prototypes, that
were allocated just once due to memory savings. Consequently gawk sometimes
failed and the error message "awk: double free or corruption" was displayed.
With this update the problem has been corrected and the error no longer occurs.

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
http://rhn.redhat.com/errata/RHBA-2012-0385.html