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 513317 - Null pointer crash in excel_read_SELECTION()
Null pointer crash in excel_read_SELECTION()
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: 2008-01-30 23:55 UTC by sum1
Modified: 2008-01-31 03:11 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
fuzzed sort.xls (15.00 KB, application/vnd.ms-excel)
2008-01-30 23:56 UTC, sum1 		Details

Description sum1 2008-01-30 23:55:33 UTC 
Version: r16315
OS: Ubuntu Gutsy

The upcoming sample is a fuzzed version of sort.xls.

Steps to reproduce:
- Load the upcoming attachment in Gnumeric to trigger a crash

Backtrace:

Program received signal SIGSEGV, Segmentation fault.

+ Trace 187504

Thread NaN (LWP 23335)

  • #0 excel_read_SELECTION
    at ms-excel-read.c line 3859
  • #1 excel_read_sheet
    at ms-excel-read.c line 5812
  • #2 excel_read_BOF
    at ms-excel-read.c line 6217
  • #3 excel_read_workbook
    at ms-excel-read.c line 6285
  • #4 excel_file_open
    at boot.c line 191
  • #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 294
  • #8 wb_view_new_from_input
    at workbook-view.c line 1212
  • #9 wb_view_new_from_uri
    at workbook-view.c line 1264
  • #10 main
    at main-application.c line 395 






Comment 1


sum1





          2008-01-30 23:56:17 UTC
        



Created attachment 104083 [details]
fuzzed sort.xls






Comment 2


Morten Welinder





          2008-01-31 03:11:55 UTC
        



This problem has been fixed in our software repository. The fix will go into the next software release. Thank you for your bug report.