#9583: Unhandled SIGSEGV with 4.5.2.alpha0 on t2
-----------------------+----------------------------------------------------
Reporter: mpatel | Owner: drkirkby
Type: defect | Status: new
Priority: blocker | Milestone: sage-4.5.2
Component: solaris | Keywords:
Author: | Upstream: N/A
Reviewer: | Merged:
Work_issues: |
-----------------------+----------------------------------------------------
Comment(by mpatel):
Replying to [comment:9 drkirkby]:
> It would be nice to know if there was a good way to do this in Mercurial
though. Adding patches is quite easy, but I assume there is a way to back
them out even after they have been committed.
You could try
* `hg up 14700` to check out revision 14700. To undo this, run `hg up`,
which checks out the "tip" revision.
* Or `hg revert -r 14700 libs/singular/option.pyx` to revert just
`option.pyx`. To undo this, run `hg revert --all`, which should revert
all files to their "tip" version.
You also could try `patch -R` with the original patch, though I haven't
done this. But I think the complexity of undoing just a given patch
depends on whether subsequent commits modified the same files.
By the way, there's also `hg bisect`, which I didn't use above because I
had 4.5.1 + an unfinished queue available. But we might find it
[http://stackoverflow.com/questions/2511704/is-there-a-recommended-
command-for-hg-bisect-command useful] for tracking down doctest failures,
crashes, etc.
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/9583#comment:10>
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.
