Rudolph Froger added the comment:
Thanks all for the fixes!
--
___
Python tracker
<https://bugs.python.org/issue32849>
___
___
Python-bugs-list mailin
Rudolph Froger <rudolphfro...@dreamsolution.nl> 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!
--
__
Rudolph Froger <rudolphfro...@dreamsolution.nl> 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
Rudolph Froger <rudolphfro...@dreamsolution.nl> 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 pro
Change by Rudolph Froger <rudolphfro...@dreamsolution.nl>:
--
type: -> crash
___
Python tracker <rep...@bugs.python.org>
<https://bugs.pyt
New submission from Rudolph Froger <rudolphfro...@dreamsolution.nl>:
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
