[bug #16475] Use of potentially uninitialized variables

[Jerker Bäck]

URL:
  <http://savannah.gnu.org/bugs/?func=detailitem&item_id=16475>

                 Summary: Use of potentially uninitialized variables
                 Project: make
            Submitted by: jerker_back
            Submitted on: Monday 05/01/06 at 11:14
                Severity: 3 - Normal
              Item Group: Bug
                  Status: None
                 Privacy: Public
             Assigned to: None
             Open/Closed: Open
       Component Version: 3.81
        Operating System: Any
           Fixed Release: None

    _______________________________________________________

Details:

When linking with the MS linker the following warnings is issued due to
possible use of variables with undefined values.

variable.c(1394) : warning C4701: potentially uninitialized local variable
'origin' used
job.c(570) : warning C4701: potentially uninitialized local variable 'status'
used
job.c(677) : warning C4701: potentially uninitialized local variable
'exit_code' used
job.c(677) : warning C4701: potentially uninitialized local variable
'exit_sig' used
job.c(728) : warning C4701: potentially uninitialized local variable
'coredump' used
main.c(2225) : warning C4701: potentially uninitialized local variable
'status' used

Even if it may or may not be possible for the variables to be used
uninitialized when looking at the actual code, no harm is done when
initialize them to zero and get rid of the warnings.

Solution:
variable.c(1364) : const char *origin = NULL;
job.c(450) : WAIT_T status = 0;
job.c(474) : int exit_code = 0, exit_sig = 0, coredump = 0;
main.c(2143) : int status = 0;







    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?func=detailitem&item_id=16475>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/