After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 492391 - Uninitialized value used in gnm_so_line_prep_sax_parser()
Uninitialized value used in gnm_so_line_prep_sax_parser()
Status: RESOLVED FIXED
Product: Gnumeric
Classification: Applications
Component: Sheet Objects
git master
Other All
: Normal normal
: ---
Assigned To: Jody Goldberg
Jody Goldberg
Depends on:
Blocks:
 
 
Reported: 2007-11-01 16:02 UTC by sum1
Modified: 2007-11-01 18:58 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description sum1 2007-11-01 16:02:31 UTC 
Version: r16045
OS: Ubuntu Gutsy

Steps to reproduce:
- From gnumeric/src/, import test-indent.gnumeric:

G_SLICE=always-malloc ../libtool --mode=execute valgrind -q --freelist-vol=50000000 --suppressions=../test/common.supp ./gnumeric ../samples/test-indent.gnumeric

Valgrind output:
==7522== Conditional jump or move depends on uninitialised value(s)
==7522==    at 0x4123C97: gnm_so_line_prep_sax_parser (gnm-so-line.c:369)
==7522==    by 0x4171CEE: xml_sax_read_obj (xml-sax-read.c:2002)
==7522==    by 0x4171D91: xml_sax_object_start (xml-sax-read.c:2022)
==7522==    by 0x50153C1: push_child (gsf-libxml.c:495)
==7522==    by 0x50154D0: lookup_child (gsf-libxml.c:532)
==7522==    by 0x5015820: gsf_xml_in_start_element (gsf-libxml.c:602)
==7522==    by 0x50D045A: xmlParseStartTag (in /usr/lib/libxml2.so.2.6.30)
==7522==    by 0x50D98EB: xmlParseElement (in /usr/lib/libxml2.so.2.6.30)
==7522==    by 0x50D58AD: xmlParseContent (in /usr/lib/libxml2.so.2.6.30)
==7522==    by 0x50D9A2D: xmlParseElement (in /usr/lib/libxml2.so.2.6.30)
==7522==    by 0x50D58AD: xmlParseContent (in /usr/lib/libxml2.so.2.6.30)
==7522==    by 0x50D9A2D: xmlParseElement (in /usr/lib/libxml2.so.2.6.30)
Comment 1 Morten Welinder 2007-11-01 18:58:59 UTC 
This problem has been fixed in the development version. The fix will be available in the next major software release. Thank you for your bug report.