UmfPack uninitiallized variable

Submitted by João Rui Leal

Assigned to Nobody

Link to original bugzilla bug (#911)
Version: 3.2
Operating system: Linux

Description

Created attachment 504
c++ main file

The variable m_extractedDataAreDirty is always used before it is initialized.

Verified with valgrid with the attached program.
Valgrind output is the following (could not attach 2 files):

==5144== Memcheck, a memory error detector
==5144== Copyright (C) 2002-2013, and GNU GPL'd, by Julian Seward et al.
==5144== Using Valgrind-3.10.0.SVN and LibVEX; rerun with -h for copyright info
==5144== Command: ./umfpackbug
==5144==
==5144== Conditional jump or move depends on uninitialised value(s)
==5144== at 0x406AC3: Eigen::UmfPackLU<Eigen::SparseMatrix<double, 0, int> >::matrixL() const (UmfPackSupport.h:169)
==5144== by 0x40626D: main (umfpackbug.cpp:18)
==5144== Uninitialised value was created by a stack allocation
==5144== at 0x4061AD: main (umfpackbug.cpp:8)
==5144==
==5144== Conditional jump or move depends on uninitialised value(s)
==5144== at 0x40728C: Eigen::UmfPackLU<Eigen::SparseMatrix<double, 0, int> >::extractData() const (UmfPackSupport.h:344)
==5144== by 0x406AD0: Eigen::UmfPackLU<Eigen::SparseMatrix<double, 0, int> >::matrixL() const (UmfPackSupport.h:169)
==5144== by 0x40626D: main (umfpackbug.cpp:18)
==5144== Uninitialised value was created by a stack allocation
==5144== at 0x4061AD: main (umfpackbug.cpp:8)
==5144==
==5144==
==5144== HEAP SUMMARY:
==5144== in use at exit: 0 bytes in 0 blocks
==5144== total heap usage: 102 allocs, 102 frees, 14,385 bytes allocated
==5144==
==5144== All heap blocks were freed -- no leaks are possible
==5144==
==5144== For counts of detected and suppressed errors, rerun with: -v
==5144== ERROR SUMMARY: 2 errors from 2 contexts (suppressed: 0 from 0)

Attachment 504, "c++ main file":
umfpackbug.cpp