From f83575f08447e91d9c26f3e9ff302b428b2c14a9 Mon Sep 17 00:00:00 2001 From: axel Date: Mon, 30 Oct 2006 07:09:11 +1000 Subject: Make sure signals aren't blocked while autoloading, also add a few consistency checks to see that signals aren't blocked in critical places darcs-hash:20061029210911-ac50b-50bec85c3d59d0332ba44f3ece1a012cdc3e8c4b.gz --- proc.c | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) (limited to 'proc.c') diff --git a/proc.c b/proc.c index e13f8a7c..72a5d12c 100644 --- a/proc.c +++ b/proc.c @@ -858,7 +858,7 @@ void job_continue (job_t *j, int cont) first_job = j; job_set_flag( j, JOB_NOTIFIED, 0 ); - debug( 4, + debug( 3, L"Continue job %d (%ls), %ls, %ls", j->job_id, j->command, @@ -895,7 +895,7 @@ void job_continue (job_t *j, int cont) } signal_unblock(); } - + /* Send the job a continue signal, if necessary. */ @@ -931,7 +931,6 @@ void job_continue (job_t *j, int cont) { int quit = 0; -// debug( 1, L"wait loop" ); /* Wait for job to report. Looks a bit ugly because it has to handle the possibility that a signal is dispatched while -- cgit v1.2.3