From: Christopher Faylor <cgf-use-the-mailinglist-please@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: Public key authorization problem with latest snapshot
Date: Sun, 30 Mar 2014 03:26:00 -0000 [thread overview]
Message-ID: <20140329192928.GB4316@ednor.casa.cgf.cx> (raw)
In-Reply-To: <5336F3E3.5000402@cornell.edu>
On Sat, Mar 29, 2014 at 12:25:07PM -0400, Ken Brown wrote:
>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!
I'm sure Corinna will be happy to hear that. She put in LONG hours
getting that issue sorted out.
I helped too, of course, by offering important "I don't like that
implementation" style feedback. It was one of those 50/50 collaborations
where one person does all the work and the other person mentions it on
a mailing list.
cgf
--
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
next prev parent reply other threads:[~2014-03-29 19:29 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-19 16:46 Ken Brown
2014-03-19 17:05 ` Corinna Vinschen
2014-03-19 19:35 ` Ken Brown
2014-03-19 20:51 ` Corinna Vinschen
2014-03-19 22:20 ` Corinna Vinschen
2014-03-20 0:01 ` Andrey Repin
2014-03-20 16:20 ` Corinna Vinschen
2014-03-30 1:27 ` Ken Brown
2014-03-30 3:26 ` Christopher Faylor [this message]
2014-03-30 6:15 ` Larry Hall (Cygwin)
2014-03-30 17:11 ` Christopher Faylor
2014-03-31 8:31 ` briansw
2014-03-31 10:19 ` Corinna Vinschen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20140329192928.GB4316@ednor.casa.cgf.cx \
--to=cgf-use-the-mailinglist-please@cygwin.com \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).