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:date:from:reply-to:message-id:to:subject
	:in-reply-to:references:mime-version:content-type
	:content-transfer-encoding; q=dns; s=default; b=Rrb6PGtotug31c4x
	hrV0XctjycqZ4u3TbVQz7kVjcMp8raLZ8Qmmk6/vvd/mG1BccMYyhmbDNTHPjPQN
	mJCYIbZp0k6TbyPPP7pJUqXoLLvO7xk5qsXJcgtJyB8KiFWwNE8am5YMMHs+T4jo
	2spALNfq8T/M5SsMjDQ3cqDMcdo=
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:date:from:reply-to:message-id:to:subject
	:in-reply-to:references:mime-version:content-type
	:content-transfer-encoding; s=default; bh=z7IhHMx74a6TLy3BFkCbtQ
	fqlzo=; b=u9I/wVRKqPnS5Efkn7zKBrs4AoYAataB5q4O5Yc7u5+wmkPGKIOpO/
	SgSwyhnENFRbWnq34nEGFl6uysDWR0acXCXoLoXgBScko2X2SogNkoE/1ZAFhkGB
	p5oe0RJ/By+CWe5Rknm4nXG/+0xesk3OkD+jgUR1eAEbZUSTzreQE=
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.com>
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
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=-3.3 required=5.0 tests=AWL,BAYES_50,FREEMAIL_FROM,KAM_THEBAT,SPF_SOFTFAIL autolearn=no version=3.3.2
X-HELO:	smtpback.ht-systems.ru
Date:	Thu, 20 Mar 2014 01:58:43 +0400
From:	Andrey Repin <anrdaemon AT yandex DOT ru>
Reply-To:	cygwin AT cygwin DOT com
Message-ID:	<885290127.20140320015843@yandex.ru>
To:	Corinna Vinschen <cygwin AT cygwin DOT com>
Subject:	Re: Public key authorization problem with latest snapshot
In-Reply-To:	<20140319170508.GF2715@calimero.vinschen.de>
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>
MIME-Version:	1.0
X-IsSubscribed:	yes

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.


--
WBR,
Andrey Repin (anrdaemon AT yandex DOT ru) 20.03.2014, <01:56>

Sorry for my terrible english...


--
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

- Raw text -