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 586066 - Null pointer crash in gnm_so_filled_write_xml_sax
Null pointer crash in gnm_so_filled_write_xml_sax
Status: RESOLVED FIXED
Product: Gnumeric
Classification: Applications
Component: General
git master
Other All
: Normal critical
: ---
Assigned To: Jody Goldberg
Jody Goldberg
Depends on:
Blocks:
 
 
Reported: 2009-06-16 23:07 UTC by sum1
Modified: 2009-06-17 01:11 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description sum1 2009-06-16 23:07:35 UTC 
Steps to reproduce:
- Download Attachment 21725 [details] (.xls file from Bug 127756)
- ssconvert attachment.xls /tmp/foo.gnumeric


Backtrace:

Program received signal SIGSEGV, Segmentation fault.

+ Trace 216036

Thread 3066476304 (LWP 3862)

  • #0 gnm_so_filled_write_xml_sax
    at gnm-so-filled.c line 341
  • #1 xml_write_objects
    at xml-sax-write.c line 1101
  • #2 xml_write_sheet
    at xml-sax-write.c line 1174
  • #3 xml_write_sheets
    at xml-sax-write.c line 1193
  • #4 gnm_xml_file_save
    at xml-sax-write.c line 1326
  • #5 go_file_saver_save_real
    at file.c line 443
  • #6 go_file_saver_save
    at file.c line 705
  • #7 wbv_save_to_output
    at workbook-view.c line 971
  • #8 wb_view_save_to_uri
    at workbook-view.c line 1008
  • #9 wb_view_save_as
    at workbook-view.c line 1044
  • #10 convert
    at ssconvert.c line 534
  • #11 main
    at ssconvert.c line 601 






Comment 1


Andreas J. Guelzow





          2009-06-17 00:50:00 UTC
        



In gnm_so_filled_init we have:

	sof->text = g_strdup (""); /* If we initialize with NULL, the canvas item */
	                           /* does not react on changes */

So it would be nice to know who is changing sof->text to NULL.






Comment 2


Andreas J. Guelzow





          2009-06-17 01:11:40 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.