Home GnuPG
Diffusion GnuPG ce98524554ca

Do not use pth functions after pth_kill. Fixes bug#1320.
ce98524554caUnpublished

Unpublished Commit · Learn More

Not On Permanent Ref: This commit is not an ancestor of any permanent ref.

Description

Do not use pth functions after pth_kill. Fixes bug#1320.

Fabian Keil found the reason for a SIGBUS:

In the "gpg-agent --daemon" case, main() calls pth_kill()
after the client has been forked, so when es_deinit() is
called on exit, acquiring the estream_list_lock seems to
cause pth to dereference a pointer located in a memory
region that has previously been free()'d.

My approach to fix it is different than his suggestion. It should
allow to continue all estream operations after a pth_kill except for
restarting pth.

Details

Provenance
wernerAuthored on Apr 29 2011, 10:16 AM
Parents
rG1226772ffd37: Fix translaor email
Branches
Unknown
Tags
Unknown

Event Timeline

werner mentioned this in Unknown Object (Maniphest Task).Mar 27 2017, 5:04 PM
werner mentioned this in Unknown Object (Maniphest Task).Mar 27 2017, 5:27 PM
werner mentioned this in Unknown Object (Maniphest Task).Mar 30 2017, 6:59 PM