Rudolph Froger added the comment:
Thanks all for the fixes!
--
___
Python tracker
<https://bugs.python.org/issue32849>
___
___
Python-bugs-list mailin
Rudolph Froger added the comment:
> Could it be simply because daemon is respawned from a process that does have
> a valid stdin at the time of respawn?
Yes, that could certainly be the case. Thanks!
--
___
Python tracker
<https://bugs.p
Rudolph Froger added the comment:
Thanks for all the research!
My crashing Python process is started by a shell process which is launched by
the Freebsd daemon tool, this might explain why stdin in no longer valid. But
I'm not sure why it can be solved, sometimes, by restarting th
Rudolph Froger added the comment:
I've tried your quick tests a few times but couldn't reproduce it immediately.
The problem is a bit hard to reproduce anyway because launching Python
processes can go well for a long time (many days; launching many processes
every minute) until su
Change by Rudolph Froger :
--
type: -> crash
___
Python tracker
<https://bugs.python.org/issue32849>
___
___
Python-bugs-list mailing list
Unsubscrib
New submission from Rudolph Froger :
Sometimes a new Python 3.6.4 process is aborted by the kernel (FreeBSD 11.1)
(before loading my Python files).
Found in syslog:
kernel: pid 22433 (python3.6), uid 2014: exited on signal 6 (core dumped)
Fatal Python error: Py_Initialize: can't initi
