GNU bug report logs - #25875
26.0.50; Hang logging out of MS-Windows

Previous Next

Full log

View this message in rfc822 format

From: Richard Copley <rcopley <at> gmail.com>
To: Eli Zaretskii <eliz <at> gnu.org>
Cc: 25875 <at> debbugs.gnu.org, Ken Brown <kbrown <at> cornell.edu>
Subject: bug#25875: 26.0.50; Hang logging out of MS-Windows
Date: Mon, 27 Feb 2017 19:23:21 +0000

On 27 February 2017 at 19:16, Eli Zaretskii <eliz <at> gnu.org> wrote:
>> From: Richard Copley <rcopley <at> gmail.com>
>> Date: Mon, 27 Feb 2017 19:04:23 +0000
>> Cc: Ken Brown <kbrown <at> cornell.edu>, 25875 <at> debbugs.gnu.org
>>
>> >> > +static LRESULT WINAPI
>> >> > +DebugSendMessage (HWND hWnd, UINT Msg, WPARAM wParam, LPARAM lParam)
>> >> > +{
>> >> > +  return SendMessageTimeoutA (hWnd, Msg, wParam, lParam, 0, 100, NULL);
>> >> > +}
>> >> > +
>> >> >  /* Start update of window W.  */
>> >> >
>> >> >  static void
>> >> >
>> >> > Ken
>> >>
>> >> Sorry Ken, I can't sabotage myself like that, I have work to do.
>> >
>> > This could be a misunderstanding: the above change is not supposed to
>> > sabotage anything, it's supposed to be a 100% compatible change for
>> > the current behavior when all threads are running, and also provide a
>> > "fire escape" when the addressee of the message is for some reason
>> > stuck, as we think happens in your scenario.
>>
>> >From the docs for SendMessageTimeout:
>>   "If the function succeeds, the return value is nonzero.".
>> We're going to cast that to HWND and pretend it's a scrollbar?
>
> No, the result is returned in the last argument of SendMessageTimeout
> (which shouldn't be NULL for getting hold of that, of course).

My point exactly.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.