GNU bug report logs - #56487
xgselect race condition leading to abort when USE_GTK not defined

Previous Next

Full log

Message #43 received at 56487 <at> debbugs.gnu.org (full text, mbox):

From: Stefan Kangas <stefankangas <at> gmail.com>
To: Eli Zaretskii <eliz <at> gnu.org>
Cc: luangruo <at> yahoo.com, Tom Gillespie <tgbugs <at> gmail.com>, 56487 <at> debbugs.gnu.org
Subject: Re: bug#56487: xgselect race condition leading to abort when USE_GTK
 not defined
Date: Sun, 23 Feb 2025 01:35:45 +0000

Stefan Kangas <stefankangas <at> gmail.com> writes:

> Eli Zaretskii <eliz <at> gnu.org> writes:
>
>>> Cc: 56487 <at> debbugs.gnu.org
>>> From: Tom Gillespie <tgbugs <at> gmail.com>
>>> Date: Mon, 11 Jul 2022 19:20:02 -0700
>>>
>>> > No, because we don't want the different GLib event dispatch behavior
>>> > outside of GTK with native input enabled.
>>>
>>> Ok, got it. I'll see if I can figure out an alternate solution with that
>>> constraint in mind.
>>
>> TIA.
>>
>>> Should I split out the release_select_lock change into a separate
>>> patch so that we can get that merged independent of a fix for the
>>> abort behavior?
>>
>> Yes, I think that's a good idea.
>
> (That was one year ago.)
>
> Tom, did you get any further here?  For example, the second part (a
> separate patch for release_select_lock) sounds useful independently of
> the rest.
>
> Thanks in advance.

Ping.  Any news here?

Previous Next

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