GNOME Bugzilla – Bug 306640
crashes when importing 500-line 2-column text from clipboard
Last modified: 2005-06-07 19:53:19 UTC
Distribution: Debian 3.1 Package: Gnumeric Severity: normal Version: GNOME2.8.3 unspecified Gnome-Distributor: Debian Synopsis: crashes when importing 500-line 2-column text from clipboard Bugzilla-Product: Gnumeric Bugzilla-Component: import/export Text Bugzilla-Version: unspecified BugBuddy-GnomeVersion: 2.0 (2.8.1) Description: Description of the crash: I have a data set I'm trying to copy into gnumeric. It's made of two columns, 1000 lines in total. I want to copy it from the xterm (the xterm only records 500 lines, so I pipe the data through "head -490"). Gnumeric's C-v paste does not recognise the clipboard formed by highlighting with the left mouse button, so I use Gnome terminal as the xterm, and use its Ctrl-Shift-c to copy the data. When I Ctrl-v this data (490 lines, 2 entries each) into gnumeric, I get the text-import dialog box. I click "forward" to select the data import criteria. Gnumeric assumes the columns are separated by spaces, but there are spaces and tabs so the default number of columns is wrong. I click on "tab" to add it to "space" (which is selected by default), then I click on "treat two separators as one". Instead of seeing the sample of imported columns displayed at the bottom of the dialog box collapse from several columns down to just two, gnumeric crashes. Steps to reproduce the crash: 1. Copy 500-odd lines of two-column data, separated by spaces and/or tabs. e.g. running python from the command line for i in range(166): ... print repr(3*i) + "\t" + "nan" ... print repr(3*i+1) + "\t " + "nan" ... print repr(3*i+2) + " \t" + "nan" then copy data from Gnome terminal using Ctrl-Shift-c. 2. Ctrl-v to paste into gnumeric. Text-import dialog comes up. 3. Press "forward" to get to second page. Imported text is shown with a mixed up number of columns. 4. Press "tab" for separator (leave "space" also selected) 5. Click on "See two separators as one". 6. gnumeric crashes Expected Results: Instead of crashing, the imported data should be tidied up in two columns (in the example given here, the first column is an integer, the second is "nan"). How often does this happen? Every time. Additional Information: The "nan" refers to "Not A Number". I am testing the limits of my calculations. However, the crash occurs just the same if integer numbers appear instead of "nan". Debugging Information: Backtrace was generated from '/usr/bin/gnumeric' (no debugging symbols found) Using host libthread_db library "/lib/tls/libthread_db.so.1". (no debugging symbols found) `system-supplied DSO at 0xffffe000' has disappeared; keeping its symbols. (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 -1222988928 (LWP 20629)] (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) 0xb769a53e in __waitpid_nocancel () from /lib/tls/libpthread.so.0
+ Trace 60610
Thread 1 (Thread -1222988928 (LWP 20629))
------- Bug moved to this database by unknown@bugzilla.gnome.org 2005-06-06 11:02 UTC ------- 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 Drew.Parsons@anu.edu.au.
What version of Gnumeric is this? Also, could you please attach a file that causes problems. That makes it far for reliable for us to verify that a problem has been fixes (as opposed to us misreading the recipe).
Sorry, I thought the bug report tool had grabbed the version. It's v1.5.1 (Debian 1.5.1-1). Which part of the recipe was unclear? You could try it with the attached file. "cat gnumeric.bad" etc.
Created attachment 47358 [details] data enabling the crash Dump this file onto a Gnome terminal (cat gnumeric.bad), then try copy&pasting into gnumeric.
This was fixed a couple of weeks ago. *** This bug has been marked as a duplicate of 305624 ***