Bug 377961 – Crash during goal seek

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 377961 - Crash during goal seek


Summary:	Crash during goal seek


Status:	RESOLVED FIXED

Product:	Gnumeric
Classification:	Applications
Component:	General
Version:	git master
Hardware:	Other All

Importance:	High critical
Target Milestone:	---
Assigned To:	Jody Goldberg
QA Contact:	Jody Goldberg

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2006-11-22 01:03 UTC by david
Modified:	2006-11-26 21:47 UTC

See Also:
GNOME target:	---
GNOME version:	2.15/2.16

Description david 2006-11-22 01:03:39 UTC

Version: 1.7.5

What were you doing when the application crashed?
I was running the goal Seeker on a relatively complex spreadsheet, to find a chi squared optimized linear fit to some data.


Distribution: Gentoo Base System version 1.12.6
Gnome Release: 2.16.1 2006-10-18 (Gentoo)
BugBuddy Version: 2.16.0

Memory status: size: 89833472 vsize: 0 resident: 89833472 share: 0 rss: 35053568 rss_rlim: 0
CPU usage: start_time: 1164126575 rtime: 0 utime: 6650 stime: 0 cutime:6429 cstime: 0 timeout: 221 it_real_value: 0 frequency: 0

Backtrace was generated from '/usr/bin/gnumeric'

(no debugging symbols found)
Using host libthread_db library "/lib/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1208424768 (LWP 11207)]
0xb7fca410 in __kernel_vsyscall ()

+ Trace 88383

Thread 1 (Thread -1208424768 (LWP 11207))

#0 __kernel_vsyscall
#1 __waitpid_nocancel
from /lib/libpthread.so.0
#2 gnome_gtk_module_info_get
from /usr/lib/libgnomeui-2.so.0
#3 <signal handler called>
#4 workbook_recalc
from /usr/lib/libspreadsheet-1.7.5.so
#5 dialog_formula_guru
from /usr/lib/libspreadsheet-1.7.5.so
#6 goal_seek_trawl_uniformly
from /usr/lib/libspreadsheet-1.7.5.so
#7 dialog_formula_guru
from /usr/lib/libspreadsheet-1.7.5.so
#8 g_cclosure_marshal_VOID__VOID
from /usr/lib/libgobject-2.0.so.0
#9 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#10 g_signal_chain_from_overridden
from /usr/lib/libgobject-2.0.so.0
#11 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#12 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#13 gtk_button_clicked
from /usr/lib/libgtk-x11-2.0.so.0
#14 gtk_button_set_alignment
from /usr/lib/libgtk-x11-2.0.so.0
#15 g_cclosure_marshal_VOID__VOID
from /usr/lib/libgobject-2.0.so.0
#16 g_value_set_boxed
from /usr/lib/libgobject-2.0.so.0
#17 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#18 g_signal_chain_from_overridden
from /usr/lib/libgobject-2.0.so.0
#19 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#20 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#21 gtk_button_released
from /usr/lib/libgtk-x11-2.0.so.0
#22 gtk_button_released
from /usr/lib/libgtk-x11-2.0.so.0
#23 gtk_marshal_BOOLEAN__VOID
from /usr/lib/libgtk-x11-2.0.so.0
#24 g_value_set_boxed
from /usr/lib/libgobject-2.0.so.0
#25 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#26 g_signal_chain_from_overridden
from /usr/lib/libgobject-2.0.so.0
#27 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#28 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#29 gtk_widget_get_default_style
from /usr/lib/libgtk-x11-2.0.so.0
#30 gtk_propagate_event
from /usr/lib/libgtk-x11-2.0.so.0
#31 gtk_main_do_event
from /usr/lib/libgtk-x11-2.0.so.0
#32 gdk_add_client_message_filter
from /usr/lib/libgdk-x11-2.0.so.0
#33 g_main_context_dispatch
from /usr/lib/libglib-2.0.so.0
#34 g_main_context_dispatch
from /usr/lib/libglib-2.0.so.0
#35 g_main_loop_run
from /usr/lib/libglib-2.0.so.0
#36 bonobo_main
from /usr/lib/libbonobo-2.so.0
#37 main
#0 __kernel_vsyscall

Comment 1 Jody Goldberg 2006-11-22 01:42:52 UTC

Please supply a sample workbook if possible and more detailed instructions.

Comment 2 Morten Welinder 2006-11-22 19:36:39 UTC

Also, could you try turning on debug information in your build?  That makes
the stack traces so much more informative.

Comment 3 Morten Welinder 2006-11-26 21:47:52 UTC

Caught it.  Fixed in cvs.

Thanks for reporting.