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 534587 - Crash in gnm_expr_eval()
Crash in gnm_expr_eval()
Status: RESOLVED FIXED
Product: Gnumeric
Classification: Applications
Component: Analytics
git master
Other All
: Normal critical
: ---
Assigned To: Morten Welinder
Jody Goldberg
Depends on:
Blocks:
 
 
Reported: 2008-05-24 04:03 UTC by sum1
Modified: 2008-05-24 17:45 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description sum1 2008-05-24 04:03:33 UTC 
Version: r16602
OS: Ubuntu Hardy

Steps to reproduce:
- Enter 'a' (no quotes) into A1
- Enter '=trend(1,1,A1,0)' (no quotes) into A2

Backtrace:

Program received signal SIGSEGV, Segmentation fault.

+ Trace 198506

Thread 3062098528 (LWP 489)

  • #0 gnm_expr_eval
    at expr.c line 1337
  • #1 gnm_expr_top_eval
    at expr.c line 2839
  • #2 gnm_cell_eval_content
    at dependent.c line 1450
  • #3 gnm_rendered_value_new
    at rendered-value.c line 210
  • #4 gnm_cell_render_value
    at cell.c line 469
  • #5 row_calc_spans
    at cellspan.c line 411
  • #6 sheet_range_bounding_box
    at sheet.c line 2250
  • #7 scg_redraw_range
    at sheet-control-gui.c line 147
  • #8 sc_redraw_range
    at sheet-control.c line 89
  • #9 sheet_redraw_partial_row
    at sheet.c line 1010
  • #10 sheet_cell_calc_span
    at sheet.c line 1102
  • #11 sheet_cell_set_text
  • #12 cmd_set_text_redo
    at commands.c line 851
  • #13 command_push_undo
    at commands.c line 742
  • #14 cmd_set_text
  • #15 wbcg_edit_finish
    at wbc-gtk-edit.c line 222
  • #16 cb_gee_key_press_event
    at gnumeric-expr-entry.c line 507
  • #17 _gtk_marshal_BOOLEAN__BOXED
    at /build/buildd/gtk+2.0-2.12.9/gtk/gtkmarshalers.c line 84 






Comment 1


Morten Welinder





          2008-05-24 17:45: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.