Bug 99170 - gawk-3.1.3 mishandling of uninitialized variables
gawk-3.1.3 mishandling of uninitialized variables
Status: CLOSED RAWHIDE
Product: Red Hat Raw Hide
Classification: Retired
Component: gawk (Show other bugs)
1.0
All Linux
medium Severity medium
: ---
: ---
Assigned To: Florian La Roche
Brock Organ
http://mail.gnu.org/archive/html/bug-...
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2003-07-15 09:58 EDT by Bill Rugolsky, Jr.
Modified: 2007-04-18 12:55 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2003-07-15 12:18:17 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Bill Rugolsky, Jr. 2003-07-15 09:58:49 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.2.1) Gecko/20030225

Description of problem:
The patch at the above URL from the gawk maintainer is needed so that
uninitialized variables passed to functions and used in a scalar context do not
generate an internal error.  Without the patch, the following fails:

function f(x) { return x }

BEGIN {
   f(z) 
   f(z) # this second invocation generates an internal error
   exit 0
}


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

How reproducible:
Always

Steps to Reproduce:
1. Test code in bug.gawk
2. gawk -f bug.gawk

Actual Results:  $ gawk -f bug.gawk
gawk: bug.gawk:5: fatal error: internal error
Aborted

Expected Results:  Exits silently.

Additional info:

gawk-3.1.3 has many additional changes to io.c.  There were numerous I/O
problems in 3.1.2 related to the I/O rewrite, which seem to have been resolved,
but there may be dragons.
Comment 1 Florian La Roche 2003-07-15 12:18:17 EDT
http://people.redhat.com/laroche/ contains the new src.rpm. Thanks for putting in
this bugzilla request,

Florian La Roche

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