GNOME Bugzilla – Bug 747210
valgrind errors with docs-samples.gnumeric
Last modified: 2015-04-01 23:16:48 UTC
This cannot be good! ../tools/gnmvalgrind ./ssconvert ../samples/docs-samples.gnumeric ~/d.ods Setting G_SLICE=always-malloc Setting GNM_DEBUG=valgrind-bitfield-workarounds Executing ../libtool --mode=execute valgrind --num-callers=40 --suppressions=../test/common.supp --suppressions=../test/gui.supp ./ssconvert ../samples/docs-samples.gnumeric /home/welinder/d.ods ==27553== Memcheck, a memory error detector ==27553== Copyright (C) 2002-2013, and GNU GPL'd, by Julian Seward et al. ==27553== Using Valgrind-3.10.0.SVN and LibVEX; rerun with -h for copyright info ==27553== Command: /home/welinder/gnome/gnumeric/src/.libs/lt-ssconvert ../samples/docs-samples.gnumeric /home/welinder/d.ods ==27553== ** (/home/welinder/gnome/gnumeric/src/.libs/lt-ssconvert:27553): WARNING **: Running under buggy valgrind, see http://bugs.kde.org/show_bug.cgi?id=164298 ==27553== Invalid read of size 2 ==27553== at 0x4C2F7E0: memcpy@@GLIBC_2.14 (in /usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so) ==27553== by 0x14B62AE4: gnumeric_replaceb (string3.h:51) ==27553== by 0x4EF26CC: function_call_with_exprs (func.c:2101) ==27553== by 0x4EE9C1C: gnm_expr_eval (expr.c:1453) ==27553== by 0x4EEA63E: gnm_expr_top_eval (expr.c:3121) ==27553== by 0x4EE0521: cell_dep_eval (dependent.c:1665) ==27553== by 0x4EE06DA: dependent_eval (dependent.c:1755) ==27553== by 0x4EE4848: workbook_recalc (dependent.c:2869) ==27553== by 0x4F9761C: workbook_view_new_from_input (workbook-view.c:1294) ==27553== by 0x4F9780B: workbook_view_new_from_uri (workbook-view.c:1337) ==27553== by 0x404285: convert (ssconvert.c:715) ==27553== by 0x403556: main (ssconvert.c:903) ==27553== Address 0x143f5b94 is 0 bytes after a block of size 4 alloc'd ==27553== at 0x4C2AB80: malloc (in /usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so) ==27553== by 0x4C2CF1F: realloc (in /usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so) ==27553== by 0x63576AE: g_realloc (in /lib/x86_64-linux-gnu/libglib-2.0.so.0.4002.0) ==27553== by 0x6370FA3: g_string_maybe_expand (in /lib/x86_64-linux-gnu/libglib-2.0.so.0.4002.0) ==27553== by 0x6370FF1: g_string_sized_new (in /lib/x86_64-linux-gnu/libglib-2.0.so.0.4002.0) ==27553== by 0x4F29581: yylex (parser.y:1356) ==27553== by 0x4F2A8AD: yyparse (parser.c:1828) ==27553== by 0x4F2BC24: gnm_expr_parse_str (parser.y:1580) ==27553== by 0x4FAFC05: xml_sax_cell_content (xml-sax-read.c:2103) ==27553== by 0x5773718: gsf_xml_in_end_element (gsf-libxml.c:863) ==27553== by 0x6C3A71C: xmlParseEndTag1 (in /usr/lib/x86_64-linux-gnu/libxml2.so.2.9.1) ==27553== by 0x6C40CEA: xmlParseElement (in /usr/lib/x86_64-linux-gnu/libxml2.so.2.9.1) ==27553== by 0x6C401F7: xmlParseContent (in /usr/lib/x86_64-linux-gnu/libxml2.so.2.9.1) ==27553== by 0x6C40A92: xmlParseElement (in /usr/lib/x86_64-linux-gnu/libxml2.so.2.9.1) ==27553== by 0x6C401F7: xmlParseContent (in /usr/lib/x86_64-linux-gnu/libxml2.so.2.9.1) ==27553== by 0x6C40A92: xmlParseElement (in /usr/lib/x86_64-linux-gnu/libxml2.so.2.9.1) ==27553== by 0x6C401F7: xmlParseContent (in /usr/lib/x86_64-linux-gnu/libxml2.so.2.9.1) ==27553== by 0x6C40A92: xmlParseElement (in /usr/lib/x86_64-linux-gnu/libxml2.so.2.9.1) ==27553== by 0x6C401F7: xmlParseContent (in /usr/lib/x86_64-linux-gnu/libxml2.so.2.9.1) ==27553== by 0x6C40A92: xmlParseElement (in /usr/lib/x86_64-linux-gnu/libxml2.so.2.9.1) ==27553== by 0x6C410B9: xmlParseDocument (in /usr/lib/x86_64-linux-gnu/libxml2.so.2.9.1) ==27553== by 0x5774523: gsf_xml_in_doc_parse (gsf-libxml.c:1338) ==27553== by 0x4FB0B12: read_file_common (xml-sax-read.c:3383) ==27553== by 0x4FB0E5B: gnm_xml_file_open (xml-sax-read.c:3512) ==27553== by 0x4F975BE: workbook_view_new_from_input (workbook-view.c:1278) ==27553== by 0x4F9780B: workbook_view_new_from_uri (workbook-view.c:1337) ==27553== by 0x404285: convert (ssconvert.c:715) ==27553== by 0x403556: main (ssconvert.c:903)
This problem has been fixed in our software repository. The fix will go into the next software release. Once that release is available, you may want to check for a software upgrade provided by your Linux distribution.