| commit | 916e2f3c61dd43817b53be5c60042934843afbf5 | |
| author | Ben Kibbey <bjk@luxsci.net> | |
| Mon, 5 Sep 2016 17:16:03 +0000 (5 13:16 -0400) | ||
| committer | Ben Kibbey <bjk@luxsci.net> | |
| Mon, 5 Sep 2016 19:09:16 +0000 (5 15:09 -0400) | ||
| tree | 50a3f56277e9013a9f92c18ffbcb6951fd127f8c | treesnapshot (tar.gz zip) |
| parent | 1b8c54ba534b7ab4db889573d5f485f09513e452 | commitdiff |
Protect gpgme_wait().
From the docs:
In a multi-threaded environment, only one thread should ever call
`gpgme_wait' at any time, irregardless if CTX is specified or not.
This means that all calls to this function should be fully
synchronized by locking primitives. It is safe to start
asynchronous operations while a thread is running in `gpgme_wait'.
From the docs:
In a multi-threaded environment, only one thread should ever call
`gpgme_wait' at any time, irregardless if CTX is specified or not.
This means that all calls to this function should be fully
synchronized by locking primitives. It is safe to start
asynchronous operations while a thread is running in `gpgme_wait'.
| src/crypto.c | diffblobblamehistory |