zd nex added the comment:
Hello,
ok but it seems to me that this segfault happens always (it is not random)? So
I guess that there should be way how fix C pickle, no? Or something else should
be done with __del__ method of shelve. Because in Python2 this was normally
working. It seems to
Change by zd nex :
--
title: SIGSEGV crash on shutdown with shelve & c pickle -> Segmentation fault
on shutdown with shelve & c pickle
___
Python tracker
<https://bugs.python.
zd nex added the comment:
So I want to properly debug this? How I can debug that call dump() for pickle?
It does not seem to be possible. I guess I need to make some custom build?
--
___
Python tracker
<https://bugs.python.org/issue39
zd nex added the comment:
Hello,
so I was trying to figure out where actually is problem is. As I do not think
it is in shelve itself. So I have made different method for __setitem__ on
shelve and I have found that it is actually in pickle.dump >
Here is code which I have used
New submission from zd nex :
So currently if python code contains 1_1 it is handled as number 11. When user
uses int("1_1") it also creates 11 and when ast.literal_eval is used it is also
created instead of string. How can user get SyntaxError input on int or
literal_eval with
zd nex added the comment:
Hi,
i was looking on failing tests on attached pull request and it seems to me that
it intentionally should create new entry for saving.
Maybe that save should actually happen, but it should be fixed in different
way? From my small tests I was thinking that
zd nex added the comment:
So I was trying it again in Python 3.6.9 and 3.8.1 directly in REPL. And it
behaves same. I have tried it on two different linux boxes (both 64bit) where
I have diffrent versions. In both of them it crashes in same way .. destroy
_ast and then it crashes and
zd nex added the comment:
Okay I have managed to crash it when exit() was called and also I am attaching
output with -v
python3.8 -X faulthandler ce_test_2.py
start
end
--Return--
> /home/fractal/workspace/test_py_crash/ce_test_2.py(19)()->None
-> breakpoint()
(Pdb) exit()
Traceb
zd nex added the comment:
Okay I have tried to run it with breakpoint() but it does not crash on 3.8
--
___
Python tracker
<https://bugs.python.org/issue39
zd nex added the comment:
Ok I will try pdb
--
___
Python tracker
<https://bugs.python.org/issue39672>
___
___
Python-bugs-list mailing list
Unsubscribe:
zd nex added the comment:
Hello,
well and in 3.8 it does not crash for you? Is there some devel build of 3.9 for
ubuntu which I can try?
I have tested it on 3.7,3.8 and 3.6 and it crashed always when close was not
present or when list was called in another function
Change by zd nex :
--
versions: +Python 3.9
___
Python tracker
<https://bugs.python.org/issue39672>
___
___
Python-bugs-list mailing list
Unsubscribe:
zd nex added the comment:
So I was trying to figure out what is crash it self and it looks to me that it
is related to import. Do you know how I can properly debug this crash?
--
___
Python tracker
<https://bugs.python.org/issue39
New submission from zd nex :
Hello,
so I was transferring some our old code from Python2.7 to new and find that new
version seems to crash quite a lot. After some finding (good thing
faulthandler) I think I tracked it down to to Shelve.__del__ method > going to
C Pickle module (not pyt
14 matches
Mail list logo
