#9880: Segfault in PyNaC 0.2.0.p4
-------------------------+--------------------------------------------------
Reporter: jpflori | Owner: burcin
Type: defect | Status: needs_review
Priority: major | Milestone: sage-4.6.2
Component: symbolics | Keywords: pynac
Author: | Upstream: N/A
Reviewer: | Merged:
Work_issues: |
-------------------------+--------------------------------------------------
Comment(by vbraun):
Replying to [comment:17 jpflori]:
> * the segfault happens in a call to std::sort() in a call to compare()
because the ordering used by pynac is not a strict weak ordering. so it is
kind of random.
`std::sort` with anything but a strict weak ordering is a receipe for
disaster. It is expected to crash, and it does in the example. So you are
saying that we must never use GiNaC internal order for sorting.
I take it that `expair_is_greater_degrevlex` does implement a strict weak
ordering, so it is safe to use with `std::sort`?
Is the patch in this ticket still relevant or has this been fixed
elsewhere?
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/9880#comment:18>
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 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-trac?hl=en.
