gpgme_op_verify returns GPGME_SIG_STAT_NONE

Bart Trojanowski bart at
Sat Jun 30 05:44:01 CEST 2001

A bit more info... running it through gdb I get:

Program received signal SIGPIPE, Broken pipe.
0x40129f84 in __libc_write () from /lib/i686/
(gdb) bt
#0  0x40129f84 in __libc_write () from /lib/i686/
#1  0x4004ec70 in __DTOR_END__ ()
   from /home/1/bart/apps/gpg/gpgme/gpgme/.libs/
#2  0x400493aa in write_cb_data (dh=0x804fdc0, fd=11) at rungpg.c:978
#3  0x400494e2 in gpg_outbound_handler (opaque=0x804fdc0, pid=6144, fd=11)
    at rungpg.c:1013
#4  0x40042eae in do_select () at wait.c:224
#5  0x40042ca9 in _gpgme_wait_on_condition (c=0x804e8d0, hang=1, cond=0x0)
    at wait.c:160
#6  0x40042c6b in gpgme_wait (c=0x804e8d0, hang=1) at wait.c:152
#7  0x400443d2 in gpgme_op_verify (c=0x804e8d0, sig=0x804fdf0, text=0x804fdc0,
    r_stat=0xbffff670) at verify.c:343
#8 <snip>

Hopefully this makes a neuron fire somewhere... I just started to trace it. :)


On Fri, 29 Jun 2001, Bart Trojanowski wrote:

> In the function comments it states...
> 	GPGME_SIG_STAT_NONE:  No status - should not happen
> ... so I was curious if there is a quick fix for this.
> A bit more info just in case it helps:  I am calling gpgme_op_verify with
> a signature from gpgme_data_new_from_mem and data from
> gpgme_data_new_with_read_cb.  The callback is only called once.  The first
> time I return the first 52 bytes, the second time the next 32 bytes; 0 is
> returned both times from this function.  It is never called again. I have
> set gpgme_set_textmode(ctx,0) and gpgme_set_armor(ctx,0)... these are the
> same values from the program that generated the signature.
> So far I know that inside the _op_verify function right after the comment
> /* fixme: Put all notation data into one XML fragment */ the variable
> c->result.verify->notation is set to zero... so it's not surprising that
> GPGME_SIG_STAT_NONE is returned.
> Right off the bat it looks like I have to investigate _op_verify_start. I
> guess I have to pull up my sleeves and step through the code in gpgme.
> Cheers,
> Bart.


More information about the Gnupg-devel mailing list