Red Hat Bugzilla – Bug 680572
[abrt] gnumeric-1:1.10.13-1.fc13: Process /usr/bin/gnumeric-1.10.13 was killed by signal 11 (SIGSEGV)
Last modified: 2011-02-28 02:00:51 EST
abrt version: 1.1.14
Attached file: backtrace
cmdline: gnumeric /home/karlh/Desktop/gnumeric-bugtest.gnumeric
comment: The crash occurs because the constraint isn't preserved on the save and reload; instead of $A$1 >= 0 it says $A$1 >= #REF#. The solver doesn't check for the improper constraint on file open either.
reason: Process /usr/bin/gnumeric-1.10.13 was killed by signal 11 (SIGSEGV)
release: Fedora release 13 (Goddard)
How to reproduce
1. Open new file and enter random numbers in A1:A5
2. Set cell B1 to "=(A1-5)^2" and fill down to B5
3. Set cell B7 to "=SUM(B1:B5)"
4. Open Solver; tell it to set $B$7 -> Min by changing $A$1.
5. Add a constraint: $A$1 >= 0; click "Add"
6. Save the file and close it.
7. Open the file you just saved.
8. Open Solver and click "Solve".
Created attachment 481101 [details]
It happens here. CCing upstream.
Crash fixed here:
Saving is fine, but loading mangles the right-hand side. I'll have a look
at that too.
Reading and a further problem fixed here.
However, results are still bogus, but that's your own fault: the model
is not linear. Use the non-linear solver instead.
Should I patch the Fedora package with these, or would it be enough if the fix shipped with the next gnumeric version?
They'll ship with the next version in, I guess, a few weeks.
That ought to be good enough. The reporter can build with patches if he
really needs it before then.
Thank you for your prompt fixes---I look forward to the next version.