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 577156 - Lotus import crash
Lotus import crash
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: 2009-03-29 02:53 UTC by sum1
Modified: 2009-03-29 03:20 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
fuzzed wk1 file (4.50 KB, application/vnd.lotus-1-2-3)
2009-03-29 02:54 UTC, sum1 		Details

Description sum1 2009-03-29 02:53:12 UTC 
Version: r17249
OS: Ubuntu Intrepid

The upcoming sample is a fuzzed version of Attachment 127125 [details] (a fuzzed .wk1 file from Bug 568917).


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


Backtrace:

Program received signal SIGSEGV, Segmentation fault.

+ Trace 213956

Thread 3066005248 (LWP 21830)

  • #2 lotus_read_old
    at lotus.c line 1600
  • #0 strlen
    from /lib/tls/i686/cmov/libc.so.6
  • #1 lotus_new_string
    at lotus.c line 1870
  • #2 lotus_read_old
    at lotus.c line 1600
  • #3 lotus_read
    at lotus.c line 2372
  • #4 lotus_file_open
    at boot.c line 84
  • #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-29 02:54:03 UTC
        



Created attachment 131613 [details]
fuzzed wk1 file






Comment 2


Morten Welinder





          2009-03-29 03:20:45 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.