Bug 80672

Summary: bad source code
Product: [Retired] Red Hat Linux Reporter: d.binderman
Component: gvAssignee: Dan Williams <dcbw>
Status: CLOSED RAWHIDE QA Contact: David Lawrence <dkl>
Severity: medium Docs Contact:
Priority: medium    
Version: 8.0   
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2004-05-18 18:35:24 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description d.binderman 2002-12-29 17:32:11 UTC 
From Bugzilla Helper:
User-Agent: Mozilla/4.6 [en-gb]C-CCK-MCD NetscapeOnline.co.uk  (Win98; I)

Description of problem:

Hello there,

I have just tried to compile package gv-3.5.8-18 from Redhat 8.0

I got the following messages from the compiler.

cc: Info: process.c, line 291: In this statement, an array is being accessed outside the bounds specified for the array type. (subscrbounds)

Here is an untested patch to shut up the compiler.

./source/process.c.old ./source/process.c
*** ./source/process.c.old	Sun Dec 15 14:40:47 2002
--- ./source/process.c	Sun Dec 15 14:41:03 2002
***************
*** 272,278 ****
     pid = fork();
  
     if (pid == 0) { /* child */
!       char *argv[3];
        char *c;
  
        INFMESSAGE(child process)
--- 272,278 ----
     pid = fork();
  
     if (pid == 0) { /* child */
!       char *argv[ 4];
        char *c;
  
        INFMESSAGE(child process)


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


How reproducible:
Always

Steps to Reproduce:
1. compile with Compaq C compiler or any C compiler that
does literal constant array index checking.
2.
3.
    

Additional info:
Comment 1 Dan Williams 2004-05-18 18:35:24 UTC 
Should be fixed in 3.5.8-27