GNOME Bugzilla – Bug 161335
Edit/undelete of 1000's of rows causes core dump
Last modified: 2005-01-21 00:55:14 UTC
Distribution: SuSE Linux 9.1 (i586) Package: Gnumeric Severity: major Version: GNOME2.4.1 Gnome-Distributor: GNOME.Org Synopsis: Edit/undelete of 1000's of rows causes core dump Bugzilla-Product: Gnumeric Bugzilla-Component: General Bugzilla-Version: BugBuddy-GnomeVersion: 2.0 (2.4.0.1) Description: Description of the crash: With line chart based on 3 rows of data (by 88 columns) deleted 1900 lines. Edit/undelete causes core dump Steps to reproduce the crash: 1. load data from csv of ascii of floating points (8 decimal digits or less, 256 wide by about 4000 2. create line graphs from 3 of the lines (88 columns worth) and place over about 50 of the rows 3. delete 1900 rows of data Expected Results: core dump How often does this happen? very often (though not always). Seems to depend on speed of doing each operation in a row Additional Information: Suse 9.1 (Novell installation). Running under KDE Debugging Information: Backtrace was generated from '/opt/gnome/bin/gnumeric' (no debugging symbols found)...Using host libthread_db library "/lib/tls/libthread_db.so.1". (no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...[Thread debugging using libthread_db enabled] [New Thread 1092621248 (LWP 21336)] (no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...0xffffe410 in ?? ()
+ Trace 53544
------- Bug moved to this database by unknown@bugzilla.gnome.org 2004-12-15 00:39 ------- Unknown version in product Gnumeric. Setting version to "unspecified". Unknown platform unknown. Setting to default platform "Other". Unknown milestone "unknown" in product "Gnumeric". Setting to default milestone for this product, '---' The original reporter of this bug does not have an account here. Reassigning to the person who moved it here, unknown@bugzilla.gnome.org. Previous reporter was n0ahweigh@yahoo.com. Setting to default status "UNCONFIRMED". Setting qa contact to the default for this product. This bug either had no qa contact or an invalid one.
Appears to be a unique stack trace, according to the simple-dup-finder.
1. What gnumeric version is this? (And where did you obtain it?) 2. May we have a sample file that shows this?
I've had no luck replicating this. We could use more information please.
Very likely a dupe of 92131. *** This bug has been marked as a duplicate of 92131 ***