#13947: zn_poly segfaults during tuning and tests on OS X and Cygwin when built
on
a busy system
-------------------------------------------+--------------------------------
Reporter: jpflori | Owner: tbd
Type: defect | Status: new
Priority: major | Milestone: sage-5.8
Component: packages | Resolution:
Keywords: zn_poly spkg cygwin osx | Work issues:
Report Upstream: N/A | Reviewers:
Authors: | Merged in:
Dependencies: | Stopgaps:
-------------------------------------------+--------------------------------
Comment (by leif):
Replying to [comment:19 fbissey]:
> Ok, leif, can you put your recipe to trigger the failure in the summary?
Oh, I don't recall right now (searching logs ...), but I think I just
faked the values in `tuning.c` (generated by `tune/tune[.c]`) by modifying
`test/test.c` (i.e., added something like `{ int i; for (i=2;i<=64;i++)
tuning_info[i].mul_fft_thresh=1; }` to the beginning of `test/test.c`(?)'s
`main()`).
After running `sage -f -s zn_poly`, start a Sage subshell and enter the
build directory.
Then you can play with it, i.e., modify the code (or tuning values), and
run `make test && test/test [-quick] [tests_to_run]*` (in
`$SAGE_ROOT/spkg/build/zn_poly-0.9.p{9,10}/src/`) IIRC.
(More to come if I find the logs, otherwise also see the comments above
for more info.)
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/13947#comment:20>
Sage <http://www.sagemath.org>
Sage: Creating a Viable Open Source Alternative to Magma, Maple, Mathematica,
and MATLAB
--
You received this message because you are subscribed to the Google Groups
"sage-trac" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/sage-trac?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.