Bug 65229

Summary:	kspread crashes on saving as csv when document contains more than 1 sheet
Product:	[Applications] calligrasheets	Reporter:	Martin van Es <bugs>
Component:	general	Assignee:	Laurent Montel <montel>
Status:	RESOLVED DUPLICATE
Severity:	crash	CC:	dang
Priority:	NOR
Version:	unspecified
Target Milestone:	---
Platform:	Compiled Sources
OS:	Linux
Latest Commit:		Version Fixed In:
Attachments:	valgrind output Backtrace

Description Martin van Es 2003-09-30 13:38:39 UTC

Version:           1.2.93 (using KDE 3.1.4)
Installed from:    compiled sources
Compiler:          gcc version 3.3.1 20030626 (Debian prerelease)
OS:          Linux (i686) release 2.4.22

On saving a sheet with more than 1 sheet as CSV kspread crashes.

I see that it makes no sense saving more than 1 sheet as CSV, but 3 open sheets is the default for kspread and I only intend the save the current one.

When I remove the 2 empty sheets, saving as CSV works as expected.

Comment 1 Stefan Hetzl 2003-10-24 14:28:53 UTC

I can't reproduce this with current CVS HEAD. What settings do you use in the CSV export dialog ?

Greetings,
Stefan

Comment 2 Martin van Es 2003-10-24 17:37:43 UTC

If kspread crashes I do not reach the CSV dialog, it crashes instantly on clicking the 'save' button, or 'ok' when asked to overwrite an existing file.
This holds for both 'save as' and 'export'.
In some occasions I do succeed in saving CSV file with more than 1 sheet, but up until now I have been unsuccessful in reproducing failure or (more important) success :(

Comment 3 Clarence Dang 2003-10-25 05:20:36 UTC

Could you please run kspread under gdb (and provide a backtrace when it crashes) or run it under valgrind (and provide the errors that it generates even if kspread doesn't crash).  Valgrind will be more reliable here.  May be a duplicate of 66142.

Comment 4 Martin van Es 2003-10-25 19:25:40 UTC

Created attachment 2882 [details]
valgrind output

Comment 5 Martin van Es 2003-10-25 19:27:22 UTC

Created attachment 2883 [details]
Backtrace

kspread backtrace although not too informative I guess

Comment 6 Clarence Dang 2003-10-26 02:17:44 UTC


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