Subject: bug#21380: 25.0.50; GTK-induced segfault when scheduling timer from window-configuration-change-hook

From: Eli Zaretskii <[email-masked]>
Date: Tue, 01 Sep 2015 19:23:38 +0300

> Date: Tue, 1 Sep 2015 16:02:59 +0000
> From: Pip Cet <[email-masked]>
> Cc: [email-masked]
> 
> On Tue, Sep 1, 2015 at 4:01 PM, Eli Zaretskii <[email-masked]> wrote:
> 
>     So maybe we should introduce a special copy_sequence_no_quit function
>     that never calls QUIT, and then use it for copying the timer lists.
> 
> How would that be different from calling block_input () and binding
> Vinhibit_quit around the call to copy_sequence?

That only prevents us from reading new events from the X socket, but
what if some signal that is already pending invokes some Lisp?