On 08/17/12 10:27, Andreas Metzler wrote:
usually my /bin/sh is dash. However I have just changed my setup and
made bash /bin/sh and reran the test. It failed on the 5th invocation.
Do you have any idea why the error requires several tries to
reproduce?
Only an obvious guess: something or another is left around that causes
the successive run to fail. Please don't ask anything silly like,
"What might that be?" (I'd have a patch, if I knew. ;)
Sorry for the cheeky answer. I _do_ wish I knew. Pretty clearly,
the autogen process is, indeed, shot dead. What might cause it to
die without a death rattle though? SIGTERM, SIGHUP and SIGINT
should all be catchable and I have signal handlers for all signals
that can be caught. What if we add some delays into the signal
emissions? It feels like grasping at straws. The best answer is
for me to be able to reproduce the problem. I am not able, however.
It works for me. :(
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
