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 125436 - Gnumeric crashes after attempting `linest' function
Gnumeric crashes after attempting `linest' function
Status: RESOLVED FIXED
Product: Gnumeric
Classification: Applications
Component: Analytics
1.2.x
Other Linux
: Normal major
: ---
Assigned To: Jody Goldberg
Jody Goldberg
Depends on:
Blocks:
 
 
Reported: 2003-10-24 19:27 UTC by duckling42
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
bug report autogenerated when gnumeric crashed (13.01 KB, text/plain)
2003-10-24 19:29 UTC, duckling42
Details

Description duckling42 2003-10-24 19:27:55 UTC
error in line 518 of regression.c (general_linear_regression): should
not be reached. Gnumeric crashes after attempting `linest' function on
60 data points. y-data and
x-data seperated by 10 orders of magnitude (1e10).

Steps to reproduce the crash:
1. Get data for a line
2. Separate x- and y- data by at least 10 orders of magnitude (e.g
x/1e10)
3. =linest(x1:x10,y10:y10)

Expected Results:

Finds estimate of gradient.

How often does this happen?

Only when x- and y- values separated by 10 or more orders of magnitude.
Possibly problem with algorithm? - If this is so, perhaps just a check
to make
sure the data is valid (i.e. not separated by 1e10), and to not do
calculations
if so rather than crash.

Additional Information:

running gnumeric-1.2.1-bonobo on linux 2.4.20 under blackbox 0.65.
Comment 1 duckling42 2003-10-24 19:29:14 UTC
Created attachment 20924 [details]
bug report autogenerated when gnumeric crashed
Comment 2 Morten Welinder 2003-10-24 19:38:33 UTC
Works for me.

Please supply _precise_ instructions on how you generate this.  (What
values to put in what cells, etc.)
Comment 3 Morten Welinder 2003-10-24 20:50:52 UTC
Got it.  Pondering fix.
Comment 4 Morten Welinder 2003-10-24 21:05:03 UTC
Fixed in cvs.  (This is a loss-of-precision case so you will end up
getting #NUM errors.)