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 707024 - Segfault in scg_find_pane when opening a spreadsheet
Segfault in scg_find_pane when opening a spreadsheet
Status: RESOLVED DUPLICATE of bug 707047
Product: Gnumeric
Classification: Applications
Component: General
git master
Other Linux
: Normal normal
: ---
Assigned To: Jody Goldberg
Jody Goldberg
Depends on:
Blocks:
 
 
Reported: 2013-08-29 06:31 UTC by Einar Lielmanis
Modified: 2013-08-29 14:22 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Einar Lielmanis 2013-08-29 06:31:33 UTC 
I have a spreadsheet that after a recent archlinux package update stopped opening in gnumeric, crashing it.

Building gnumeric from the git and bisecting shows commit 55aa911c by Andreas J Guelzow on Aug 4 as the first bad commit.

I can provide this crashing xls privately.


Backtrace from the current master (5c2b855b):

Program received signal SIGSEGV, Segmentation fault.
0x00007ffff79881c2 in scg_find_pane (scg=0x7fffd4009930, pos=0x6c5a5c) at sheet-control-gui.c:3705
3705                    if (pane->first.col <= pos->col &&
(gdb) bt

+ Trace 232431

  • #0 scg_find_pane
    at sheet-control-gui.c line 3705
  • #1 scg_show_im_tooltip
    at sheet-control-gui.c line 3724
  • #2 sc_show_im_tooltip
    at sheet-control.c line 139
  • #3 sheet_view_edit_pos_tool_tips
    at sheet-view.c line 655
  • #4 sv_update
    at sheet-view.c line 684
  • #5 sheet_update
    at sheet.c line 1985
  • #6 main
    at main-application.c line 336 






Comment 1


Einar Lielmanis





          2013-08-29 06:34:18 UTC
        



Crashing .gnumeric file, not xls, of course.






Comment 2


Morten Welinder





          2013-08-29 14:22:21 UTC
        



Given the crash location, I think this is the same as bug 707047.

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