Cilly.pm ignores signals generated by cilly.asm.exe. The following patch to
Cilly.pm.in reports to
stderr the exact name of the command and the signal that it received before Cil
shifts the code. The
exit value remains the same. It might be better to heed the comment and not
repeat the command, but
printing the signal number seems important .
--- lib/Cilly.pm.in (revision 12136)
+++ lib/Cilly.pm.in (working copy)
@@ -1324,6 +1324,9 @@
# sm: now that we always print, don't echo the command again,
# since that makes the output more confusing
#die "Possible error with @cmd!\n";
+ if ($code & 0x7f) {
+ print STDERR "The command\n@cmd\nreceived signal ," ($code &0x7f), "\n";
+ }
$code >>= 8; # extract exit code portion
exit $code;
------------------------------------------------------------------------------
What You Don't Know About Data Connectivity CAN Hurt You
This paper provides an overview of data connectivity, details
its effect on application quality, and explores various alternative
solutions. http://p.sf.net/sfu/progress-d2d
_______________________________________________
CIL-users mailing list
CIL-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/cil-users
