Bug 97736 - corrupted argument values when passed to a function
Summary: corrupted argument values when passed to a function
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 2.1
Classification: Red Hat
Component: gcc
Version: 2.1
Hardware: ia64
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Jakub Jelinek
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2003-06-19 21:34 UTC by umut
Modified: 2007-11-30 22:06 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2007-10-19 19:24:48 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
c file (2.05 KB, text/plain)
2003-06-19 21:35 UTC, umut 		no flags Details
result file (467 bytes, text/plain)
2003-06-19 21:38 UTC, umut 		no flags Details
result file (467 bytes, text/plain)
2003-06-19 21:52 UTC, umut 		no flags Details
View All

Description umut 2003-06-19 21:34:20 UTC 
Description of problem:Argument values/addresses get corrupted when passed to a 
function


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


How reproducible: Always


Steps to Reproduce:
1.cc -o a a.c
2.
3.
    
Actual results:


Expected results:


Additional info: see the attached code.
Comment 1 umut 2003-06-19 21:35:52 UTC 
Created attachment 92500 [details]
c file
Comment 2 umut 2003-06-19 21:38:02 UTC 
Created attachment 92501 [details]
result file

The output of the attached c code.
Comment 3 umut 2003-06-19 21:52:53 UTC 
Created attachment 92502 [details]
result file

The output of the attached c code.
Comment 4 Richard Henderson 2004-10-03 23:39:52 UTC 
FWIW, it is fixed with 3.2.3-24 in RHEL3.
Comment 5 RHEL Program Management 2007-10-19 19:24:48 UTC 
This bug is filed against RHEL2.1, which is in maintenance phase.
During the maintenance phase, only security errata and select mission
critical bug fixes will be released for enterprise products.  Since
this bug does not meet that criteria, it is now being closed.

For more information of the RHEL errata support policy, please visit:
http://www.redhat.com/security/updates/errata/

If you feel this bug is indeed mission critical, please contact your
support representative.  You may be asked to provide detailed
information on how this bug is affecting you.
Note You need to log in before you can comment on or make changes to this bug.