What steps will reproduce the problem?
1. Run program under valgrind. Observe complaints about 0-byte allocations and
access past allocated area arising from both QSPLINE::QSPLINE(int, int*,
double*) and QSPLINE::y(double).
What is the expected output? What do you see instead?
There appears to be no visible impact to this bug other than theoretical
concerns about correctness, or at the very least none that I can identify.
What version of the product are you using? On what operating system?
Lastest SVN on OS X.
Please provide any additional information below.
The provided patch simply initializes a dummy QSPLINE with 1 set of
coefficients, all which are zero, and with valid spline value range from 0 to 1.
Original issue reported on code.google.com by alank...@bel.fi on 12 May 2014 at 11:02
Original issue reported on code.google.com by
alank...@bel.fi
on 12 May 2014 at 11:02Attachments: