On Fri, 6 Dec 2002 00:18:53 +0100 (Romance Standard Time) Vadim Zeitlin <[EMAIL PROTECTED]> wrote:
> On Thu, 5 Dec 2002 09:22:36 +0100 Xavier Nodet <[EMAIL PROTECTED]> wrote: > XN> When I had a lock, it was always because, although a gpg process does > XN> exist, the in->Write call never returns. > Where does it block? I don't know yet. But what I noticed is the following strange behavior. When I try to verify the signature of a specific message (11 kB), the VerifySignature method is called twice. This seems to be because wxYield is called, as the following trace suggests (line numbers is where I added the wxLogWarning lines): 11:41:26: Warning: Begin VerifySignature PGPEngine.cpp::738 11:41:26: Warning: Before wxExecute PGPEngine.cpp::444 11:41:26: Warning: After wxExecute (5728) PGPEngine.cpp::457 11:41:27: Warning: Before yield PGPEngine.cpp::661 11:41:27: Warning: After yield PGPEngine.cpp::661 11:41:27: Warning: Begin VerifySignature 11:41:27: Warning: Before wxExecute 11:41:27: Warning: After wxExecute (4652) Then M crashes... My understanding is that when wxYield is called, the viewer gets triggered again, and tries to verify again the message, while a previous instance of GPG already runs. And I guess the crash comes from the fact that some data are shared between the two process. Hmm... I just did this test again, and M still crashes, but just after the line "After yield" is displayed... So I do not really know what goes on, but it seems that there really is a problem, here... -- Xavier Nodet "They that can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety." - Benjamin Franklin, 1759. ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ Mahogany-Developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/mahogany-developers
