New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
%timeit unpickle_all() causes a SEGABRT #13636
Comments
This comment has been minimized.
This comment has been minimized.
comment:2
Usually asking for the stack backtrace is one of the most interesting things:
So, the error happens in NTL. I suppose that this is an error that normally gets caught appropriately but due to |
comment:3
See #10705 for another seg fault associated with unpickle_all. |
comment:4
Replying to @AndrewAtLarge:
Well ... |
comment:5
Replying to @nbruin:
OK, let's close this as a duplicate then. I'll set it as needs review. Could you please "review" it Nils? |
This comment has been minimized.
This comment has been minimized.
Reviewer: Travis Scrimshaw |
comment:6
I agree that this is a duplicate. |
CLOSED AS DUPLICATE OF #10705
The subject says it all:
Sage gives a SEGABRT with the following:
Note, however, that the following is OK:
as is calling
unpickle()
with an argument:I get this error for versions 5.3 and 5.4.rc1 running on a macbook pro with lion.
I initially thought that perhaps timeit did not like calling itself, however, this seems to be OK because the following does work:
I tried running through sage -gdb but I don't know how to interpret the outout. Here is the tail of what it produces:
Component: pickling
Reviewer: Travis Scrimshaw
Issue created by migration from https://trac.sagemath.org/ticket/13636
The text was updated successfully, but these errors were encountered: