-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hey,
I found a bug where I can cause the gprolog process to use 100% cpu when it is not calculating or solving anything, but only waiting for input. Steps to reproduce: 1) Open two separate terminals 2) In terminal 1, execute 'sh -c gprolog' The gprolog prompt appears. 3) In terminal 2, find the pid of 'sh -c gprolog' and terminate that process with kill -9 The gprolog process remains alive, but is idling near 0% cpu. The 'sh -c gprolog' is gone. 4) In terminal 1, enter some text without pressing Enter. The gprolog process is now at 100% CPU. Expected behavior: I expected gprolog to realize that its input or output streams were closed and that it should terminate. This does happen when I press Enter at step 4 without entering text. When I enter text, the CPU is at 100%, when I only press Enter the gprolog process terminates. - -- with kind regards, Kevin de Berk www.axini.com -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQEcBAEBAgAGBQJVNhtiAAoJEFTlg0HB0+E2jooH/1n/nWRVFlSzDKN0mTpq4yJr mv++k7J+NHzlsekPH4v63z93lmrGccYsQCFEQB3PXaxTPbsjNepQhSs0gtXj3zPT v/yUUGLMtQiE6F0KUJ+icIi3Fuiq/iE7XdHqCInFgEWXiT4GJDZb74aLFBskJOo6 Jc91+q7FExD4LjCm9rC886uI2vkIWr4t2rRWDfc+hATl8Gi9Qv6RFAQKt15GOXL+ qXZXvtczxwNZnnJfJ7jO6qNTNbLpj6qMY3O3CeENfVI6fVc+CpVLa4Xf/3D9vxLL xQXy2X8q2Wp/LNd48cwWan9nLxFdWJa32z6DeBqoW2NX7+Kgzzf40PfJdRpezLI= =iqcY -----END PGP SIGNATURE----- _______________________________________________ Bug-prolog mailing list Bug-prolog@gnu.org https://lists.gnu.org/mailman/listinfo/bug-prolog
