[issue33196] SEGV in mp.synchronize.Lock.__repr__ in spawn'ed proc if ctx mismatched

Arcadiy Ivanov added the comment: @vstinner > I'm not sure that I understand the bug. The bug is, if a user makes an error and passes a Queue from context 'fork' to a child that is spawned using 'spawn', the passed Queue is, for obvious reasons, broken. The 'print("Child r_q: %r, %r, %r"

[issue33196] SEGV in mp.synchronize.Lock.__repr__ in spawn'ed proc if ctx mismatched

Gus Goulart added the comment: @vstinner, on Debian 9 I can see the problem as well but wasn't able to debug with the level of details you did. Could you please share the process you followed? What I found was: ./python -X dev test_lock_sigsegv.py Parent r_q: , , Fatal Python error: Segme

[issue33196] SEGV in mp.synchronize.Lock.__repr__ in spawn'ed proc if ctx mismatched

STINNER Victor added the comment: > At a minimum I think there should be a check trying to reduce arguments via > incompatible context's process to prevent a SEGV. I'm not sure that I understand the bug. The reproducer script pass a multiprocessing.Queue to a child process and then the child

[issue33196] SEGV in mp.synchronize.Lock.__repr__ in spawn'ed proc if ctx mismatched

Change by Arcadiy Ivanov : Added file: https://bugs.python.org/file47933/coredump ___ Python tracker ___ ___ Python-bugs-list mailing list U

[issue33196] SEGV in mp.synchronize.Lock.__repr__ in spawn'ed proc if ctx mismatched

Arcadiy Ivanov added the comment: @taleinat The above has been reproduced on Fedora 29. -- ___ Python tracker ___ ___ Python-bugs-l

[issue33196] SEGV in mp.synchronize.Lock.__repr__ in spawn'ed proc if ctx mismatched

Arcadiy Ivanov added the comment: @gus.goulart you have reproduced it. The screenshot showing `-11` means the process dumped core. Because it's the child that dumps core, it's masked by abrt. Observe: $ python3 --version Python 3.7.1 $ python3 ~/Downloads/test_lock_sigsegv.py Parent r_q: ,

[issue33196] SEGV in mp.synchronize.Lock.__repr__ in spawn'ed proc if ctx mismatched

Gus Goulart added the comment: I've tested on Fedora 29 server and also failed to reproduce the error. -- Added file: https://bugs.python.org/file47931/testing_on_fedora.png ___ Python tracker __

[issue33196] SEGV in mp.synchronize.Lock.__repr__ in spawn'ed proc if ctx mismatched

Tal Einat added the comment: On Win10 I've also failed to reproduce the reported issue with the supplied script. I tried with Python versions 3.6.3, 3.7.0, and a recent build of the master branch (to be 3.8). Can someone try to reproduce this on Fedora? --

[issue33196] SEGV in mp.synchronize.Lock.__repr__ in spawn'ed proc if ctx mismatched

Change by Gus Goulart : -- nosy: +taleinat ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.pytho

[issue33196] SEGV in mp.synchronize.Lock.__repr__ in spawn'ed proc if ctx mismatched

Gus Goulart added the comment: I couldn't reproduce the error on Debian 9 nor OSX, although I tried tweaking the test script a little bit to force the error. Arcadiy, did you tried reproducing the same issue in a different platform? Did someone report something similar in recent issues on ge

[issue33196] SEGV in mp.synchronize.Lock.__repr__ in spawn'ed proc if ctx mismatched

Antoine Pitrou added the comment: Thanks for the report. Indeed I think it would be worth preventing this programmer error. -- nosy: +pitrou stage: -> needs patch versions: +Python 3.7, Python 3.8 ___ Python tracker

[issue33196] SEGV in mp.synchronize.Lock.__repr__ in spawn'ed proc if ctx mismatched

New submission from Arcadiy Ivanov : While working on GH gevent/gevent#993 I've encountered a stall trying to read from an mp.Queue passed to mp.Process's target as an argument. Trying to print out the lock state in child process I encountered as SEGV in Lock's __repr__. I originally thought i