[issue35828] test_multiprocessing_fork - crashes in PyDict_GetItem - segmentation error

2019-03-04 Thread Michael Felt
Michael Felt added the comment: I see I already asked howto better utilize this info: ConnectionRefusedError: [Errno 79] Connection refused Warning -- files was modified by test_multiprocessing_fork Before: [] After: ['core'] -- so, more specific -- which module, or file, is doing this

[issue35828] test_multiprocessing_fork - crashes in PyDict_GetItem - segmentation error

2019-02-20 Thread Michael Felt
Michael Felt added the comment: Also - this looks like a core dump was 'seen', but later removed. Warning -- files was modified by test_multiprocessing_forkserver Before: [] After: ['core'] What can I change so that ot does not cleanup the core file? --

[issue35828] test_multiprocessing_fork - crashes in PyDict_GetItem - segmentation error

2019-02-20 Thread Michael Felt
Michael Felt added the comment: Another message that surprises me is: Warning -- multiprocessing.process._dangling was modified by test_multiprocessing_spawn Before: <_weakrefset.WeakSet object at 0x3076e810> After: <_weakrefset.WeakSet object at 0x3076e390> Normally speaking the

[issue35828] test_multiprocessing_fork - crashes in PyDict_GetItem - segmentation error

2019-02-20 Thread Michael Felt
Michael Felt added the comment: I am still trying to get further with this, but I won't get far enough without some help on how to best dig deeper. For one, it should be leaving a core dump, but it never seems to leave the core dump in the working directory. I know it is doing core dump

[issue35828] test_multiprocessing_fork - crashes in PyDict_GetItem - segmentation error

2019-01-30 Thread Raymond Hettinger
Change by Raymond Hettinger : -- nosy: +davin ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue35828] test_multiprocessing_fork - crashes in PyDict_GetItem - segmentation error

2019-01-30 Thread Michael Felt
Michael Felt added the comment: After enabling PYTHONTHREADDEBUG=1 I got the dprintf output. I added line info (as fixed text) asin: Python/thread_pthread.h: +511 PyLockStatus +512 PyThread_acquire_lock_timed(PyThread_type_lock lock, PY_TIMEOUT_T microseconds, +513

[issue35828] test_multiprocessing_fork - crashes in PyDict_GetItem - segmentation error

2019-01-30 Thread Michael Felt
Michael Felt added the comment: OK. being more specific about the test situation. When I run ./python -m test test_multiprocessing_fork all is fine. However, when I run it as: ./python -m test -j2 test_multiprocessing_main_handling test_multiprocessing_fork