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 577259 - Null pointer crash in excel_read_MULBLANK
Null pointer crash in excel_read_MULBLANK
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 05:48 UTC by sum1
Modified: 2009-03-30 17:32 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
fuzzed xls file (zipped) (278.62 KB, application/zip)
2009-03-30 05:51 UTC, sum1 		Details

Description sum1 2009-03-30 05:48:30 UTC 
Version: r17254
OS: Ubuntu Intrepid

The upcoming file is a fuzzed version of Attachment 53618 [details] (.xls file from Bug 319101).


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


Backtrace:

Program received signal SIGSEGV, Segmentation fault.

+ Trace 213989

Thread 3066251008 (LWP 22000)

  • #0 excel_read_MULBLANK
    at ms-excel-read.c line 4412
  • #1 excel_read_sheet
    at ms-excel-read.c line 6250
  • #2 excel_read_BOF
    at ms-excel-read.c line 6545
  • #3 excel_read_workbook
    at ms-excel-read.c line 6628
  • #4 excel_file_open
    at boot.c line 192
  • #5 go_plugin_loader_module_func_file_open
    at go-plugin-loader-module.c line 239
  • #6 go_plugin_file_opener_open
    at go-plugin-service.c line 476
  • #7 go_file_opener_open
    at file.c line 299
  • #8 wb_view_new_from_input
    at workbook-view.c line 1058
  • #9 wb_view_new_from_uri
    at workbook-view.c line 1112
  • #10 main
    at main-application.c line 413 






Comment 1


sum1





          2009-03-30 05:51:26 UTC
        



Created attachment 131686 [details]
fuzzed xls file (zipped)






Comment 2


Morten Welinder





          2009-03-30 17:32:17 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.