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 577351 - Null pointer crash in ms_excel_chart_read
Null pointer crash in ms_excel_chart_read
Status: RESOLVED FIXED
Product: Gnumeric
Classification: Applications
Component: import/export MS Excel (tm)
git master
Other All
: Normal critical
: ---
Assigned To: Jody Goldberg
Jody Goldberg
Depends on:
Blocks:
 
 
Reported: 2009-03-30 20:08 UTC by sum1
Modified: 2009-03-30 20:56 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
fuzzed xls file (48.50 KB, application/vnd.ms-excel)
2009-03-30 20:10 UTC, sum1 		Details

Description sum1 2009-03-30 20:08:49 UTC 
Version: r17255
OS: Ubuntu Intrepid

The upcoming file is a fuzzed version of the .xls document from http://qa.openoffice.org/issues/show_bug.cgi?id=1508.


Steps to reproduce:
- Import the upcoming attachment to trigger a crash


Backtrace:

Program received signal SIGSEGV, Segmentation fault.

+ Trace 214021

Thread 3066152704 (LWP 11705)

  • #0 ms_excel_chart_read
    at ms-chart.c line 3606
  • #1 excel_read_BOF
    at ms-excel-read.c line 6554
  • #2 excel_read_workbook
    at ms-excel-read.c line 6632
  • #3 excel_file_open
    at boot.c line 192
  • #4 go_plugin_loader_module_func_file_open
    at go-plugin-loader-module.c line 239
  • #5 go_plugin_file_opener_open
    at go-plugin-service.c line 476
  • #6 go_file_opener_open
    at file.c line 299
  • #7 wb_view_new_from_input
    at workbook-view.c line 1058
  • #8 wb_view_new_from_uri
    at workbook-view.c line 1112
  • #9 main
    at main-application.c line 413 






Comment 1


sum1





          2009-03-30 20:10:09 UTC
        



Created attachment 131725 [details]
fuzzed xls file






Comment 2


Morten Welinder





          2009-03-30 20:56:33 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.