Hi, all,
On Dec 4, 2007, at 20:07 , mabshoff wrote:
[snip]
> Those are all cause by mwrank. The issue seems to be the same issue as
> Justin Walker reported in the 2.8.15 thread in sage-support.
> Interestingly nobody ever reported it and I now finally have a
> testcase that also produces the issue on sage.math under valgrind. I
> have send John Cremona two valgrind traces and hope that it will help
> to fix the issues.
An update:
FWIW, I ran mwrank on the same input as you used for your test, and
it completed without a peep, at least until I quit.
'mwrank' doesn't like it if you just exit (by typing "^D" or, more or
less equivalently, by "ending a file").
Thus, if you run 'mwrank' and give it a file containing, for example,
"[0,0,1,-1,0]" and nothing else, it will barf at the end. If your
file contains "[0,0,0,0,0]", the program sweetly closes up shop (when
it reads this) and quits.
The error I get is
bad ZZ input
Abort trap
Anyone know why this doesn't show up in the test logs? Is it worth
tracking down?
The issue is that the terminating condition for input processing in
'getcurve()' is a "null curve" (""[0,0,0,0,0]""), rather than EOF.
An EOF is an error condition, hence the abort().
A C++ mavin may know how to fix this (I don't). Trac #1402.
Justin
--
Justin C. Walker, Curmudgeon-At-Large
Institute for the Absorption of Federal Funds
--------
Men are from Earth.
Women are from Earth.
Deal with it.
--------
--~--~---------~--~----~------------~-------~--~----~
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/sage-devel
URLs: http://sage.scipy.org/sage/ and http://modular.math.washington.edu/sage/
-~----------~----~----~----~------~----~------~--~---
