X-Recipient: archive-cygwin AT delorie DOT com DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id :list-unsubscribe:list-subscribe:list-archive:list-post :list-help:sender:message-id:date:from:mime-version:to:subject :references:in-reply-to:content-type:content-transfer-encoding; q=dns; s=default; b=SlovFu4lplCNdiSOdnwddmBNTKtrM8bz3T/p/n/zSUD g6HGN8tNPKw9vY6Sjy0os1+J+VY6FEXLVusWT4Ix8eTNxzETM0LorE6Q3Hblne24 CPtGc6Z4B4LpzX/OIf2Fo6GLEZvm9idnSWtD/EKrnzr8mR0XqyrO6Wkcfi7RnSK8 = DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id :list-unsubscribe:list-subscribe:list-archive:list-post :list-help:sender:message-id:date:from:mime-version:to:subject :references:in-reply-to:content-type:content-transfer-encoding; s=default; bh=zSyYSfYYb1wSRsFQx/wHWu8hMwM=; b=s724VQwdjkJcITqH3 XHL1o5gtb9NcbwedkCsJWN147J9VVpPa5QwoTlAIf3ihEPpJ8TPMnA7+BRV7vNIc nGg3QcIG7E9aOxilPzR1YFN1PYkT2TIxoDrVNLD5VNPMfhA8CLBF1oJKkV6h7ZXv XLdx+URhOjt+nB5Q47o7WKZ4LY= Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-1.4 required=5.0 tests=AWL,BAYES_00,RCVD_IN_JMF_BR,RP_MATCHES_RCVD,SPF_PASS autolearn=no version=3.3.2 X-HELO: limerock03.mail.cornell.edu X-CornellRouted: This message has been Routed already. Message-ID: <5336F3E3.5000402@cornell.edu> Date: Sat, 29 Mar 2014 12:25:07 -0400 From: Ken Brown User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.4.0 MIME-Version: 1.0 To: cygwin AT cygwin DOT com Subject: Re: Public key authorization problem with latest snapshot References: <5329B9D0 DOT 6070703 AT cornell DOT edu> <20140319160914 DOT GD2715 AT calimero DOT vinschen DOT de> <5329C9EF DOT 1000305 AT cornell DOT edu> <20140319170508 DOT GF2715 AT calimero DOT vinschen DOT de> <885290127 DOT 20140320015843 AT yandex DOT ru> <20140320150258 DOT GD3729 AT calimero DOT vinschen DOT de> In-Reply-To: <20140320150258.GD3729@calimero.vinschen.de> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-IsSubscribed: yes On 3/20/2014 11:02 AM, Corinna Vinschen wrote: > On Mar 20 01:58, Andrey Repin wrote: >> Greetings, Corinna Vinschen! >> >>> The code is now practically equivalent to what is in 1.7.28. Only the >>> VectoredContinueHandler, which was the reason Cygwin's exception handler >>> could be called twice, is not called anymore. Instead there's a vectored >>> exception handler which is only called during debugging. >> >>> Before: >> >>> if (!handler_installed) >>> { >>> handler_installed = true; >>> SetUnhandledExceptionFilter (handle); >>> AddVectoredContinueHandler (1, handle); >>> } >> >>> After: >> >>> if (!handler_installed) >>> { >>> handler_installed = true; >>> SetUnhandledExceptionFilter (handle); >>> AddVectoredExceptionHandler (1, handle_while_being_debugged); >>> } >> >>> If anybody can explain this weird behaviour, please educate me. >> >> I can't explain the behavior, but I could say, that setting >> "handler_installed = true;" before the handler is actually installed is not >> quite right. >> Unless that variable is used inside either of two functions called afterward, >> I would move it down to the end of `if' block. > > BTDT. This isn't the problem. I *may* have found the culprit today, > but I ripped apart a lot of the code so I'm not really sure yet. Stay > tuned. The problems I've reported seem to all be fixed in the latest snapshot (2014-03-29 15:21:43 UTC). Thanks! Ken -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple