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 517376 - Another crash in expr_stack_pop()
Another crash in expr_stack_pop()
Status: RESOLVED FIXED
Product: Gnumeric
Classification: Applications
Component: import/export other
git master
Other All
: Normal critical
: ---
Assigned To: Morten Welinder
Jody Goldberg
Depends on:
Blocks:
 
 
Reported: 2008-02-19 04:30 UTC by sum1
Modified: 2008-02-19 14:25 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
fuzzed poker.wb2 (612.85 KB, application/x-quattropro)
2008-02-19 04:34 UTC, sum1 		Details

Description sum1 2008-02-19 04:30:43 UTC 
Version: r16381 (includes the fix for Bug 517144)
OS: Ubuntu Gutsy

The upcoming sample is a fuzzed version of poker.wb2.

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

Backtrace:

Program received signal SIGSEGV, Segmentation fault.

+ Trace 189694

Thread NaN (LWP 32045)

  • #0 expr_stack_pop
    at qpro-read.c line 338
  • #1 qpro_parse_formula
    at qpro-read.c line 574
  • #2 qpro_read_sheet
    at qpro-read.c line 737
  • #3 qpro_read_workbook
    at qpro-read.c line 845
  • #4 qpro_file_open
    at qpro-read.c line 886
  • #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 417 






Comment 1


sum1





          2008-02-19 04:34:08 UTC
        



Created attachment 105559 [details]
fuzzed poker.wb2






Comment 2


Morten Welinder





          2008-02-19 14:25:04 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.