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 727285 - Crash when opening .gnumeric file
Crash when opening .gnumeric file
Status: RESOLVED DUPLICATE of bug 707047
Product: Gnumeric
Classification: Applications
Component: General
1.12.x
Other Linux
: Normal major
: ---
Assigned To: Jody Goldberg
Jody Goldberg
Depends on:
Blocks:
 
 
Reported: 2014-03-29 06:45 UTC by Markus Bertheau
Modified: 2014-03-29 08:28 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
The file that crashes gnumeric upon opening (18.85 KB, application/x-gnumeric)
2014-03-29 06:45 UTC, Markus Bertheau
Details

Description Markus Bertheau 2014-03-29 06:45:05 UTC
Created attachment 273216 [details]
The file that crashes gnumeric upon opening

Opening the attached .gnumeric file immediately crashes gnumeric.
Comment 1 Markus Bertheau 2014-03-29 07:38:34 UTC
Here's a stack trace (Ubuntu saucy everything current, gnumeric 1.12.6)

Program received signal SIGSEGV, Segmentation fault.
scg_find_pane (pos=0x555555781adc, scg=0x555555ea1930)
    at sheet-control-gui.c:3705
3705	sheet-control-gui.c: No such file or directory.
(gdb) bt
  • #0 scg_find_pane
    at sheet-control-gui.c line 3705
  • #1 scg_show_im_tooltip
    at sheet-control-gui.c line 3724
  • #2 sheet_view_edit_pos_tool_tips
    at sheet-view.c line 655
  • #3 sv_update
    at sheet-view.c line 684
  • #4 sheet_update
    at sheet.c line 1985
  • #5 main
    at main-application.c line 336

Comment 2 Markus Bertheau 2014-03-29 07:44:47 UTC
It crashes because scg->pane[1] is NULL:

(gdb) print scg->pane
$5 = {0x555555fce100, 0x0, 0x0, 0x555555fce3e0}
Comment 3 Jean Bréfort 2014-03-29 08:00:47 UTC
I'm unable to reproduce with current trunk. Which exact version are you running?
Comment 4 Jean Bréfort 2014-03-29 08:28:31 UTC

*** This bug has been marked as a duplicate of bug 707047 ***