Trace the use of GPG_ERR_INV_ENGINE.

* src/debug.h: Include "gpgme.h"
(_gpgme_trace_gpgme_error): New.
(trace_gpg_error): New macro.  Use it in all files where we return
GPG_ERR_INV_ENGINE; also "include debug.h" as needed.
--

This is a pretty common error code but often it is hard to figure out
the actual cause.  With debug level 4 we now print the file name and
line number where this error code is generated by gpgme.  Along with
the git revision printed in the first log lines, this should give us
an easier way to track down the problems related to this error code.

1 files changed, 3 insertions, 3 deletions

diff --git a/src/decrypt.c b/src/decrypt.c
index f4f95dc9..63787c70 100644
--- a/src/decrypt.c
+++ b/src/decrypt.c
@@ -146,7 +146,7 @@ parse_enc_to (char *args, gpgme_recipient_t *recp)
   if (*args != '\0' && *args != ' ')
     {
       free (rec);
-      return gpg_error (GPG_ERR_INV_ENGINE);
+      return trace_gpg_error (GPG_ERR_INV_ENGINE);
     }
 
   while (*args == ' ')
@@ -160,7 +160,7 @@ parse_enc_to (char *args, gpgme_recipient_t *recp)
 	{
 	  /* The crypto backend does not behave.  */
 	  free (rec);
-	  return gpg_error (GPG_ERR_INV_ENGINE);
+	  return trace_gpg_error (GPG_ERR_INV_ENGINE);
 	}
     }
 
@@ -283,7 +283,7 @@ _gpgme_decrypt_status_handler (void *priv, gpgme_status_code_t code,
 	  }
 	/* FIXME: Is this ok?  */
 	if (!rec)
-	  return gpg_error (GPG_ERR_INV_ENGINE);
+	  return trace_gpg_error (GPG_ERR_INV_ENGINE);
       }
       break;