Re: C-g crash redux

[Kim F. Storm]

Nick Roberts <address@hidden> writes:

> Romain Francoise writes:
>  > I can crash Emacs reliably with current (Aug 2nd) sources by hitting C-g
>  > while it's preparing a partial-completion-mode prompt.  I just did it
>  > three times in a row.  The Lisp backtrace shows that it's indeed related
>  > to sit-for:
>
> Emacs can be made to crash simply by evaluating (sit-for 4) in the scratch
> buffer and typing C-g before four seconds elapse.
>
> It's due to this change:
>
> 2006-08-01  Kim F. Storm  <address@hidden>
>
>       * process.c (wait_reading_process_output_unwind): New function.
>       Restores waiting_for_user_input_p to saved value.
>       (wait_reading_process_output): Unwind protect waiting_for_user_input_p
>       instead of save/restore old value on stack.
>
> Presumably wait_reading_process_output is interrupted before it can do:
>
>   unbind_to (count, Qnil);

Huh?  Is that really possible?

What kind of interrupt can cause unwind_protect forms NOT to be run?

I don't have time to look at this right now.

Could someone pls. investigate this.  (It is trivial to
reproduce as Nick describes above).

-- 
Kim F. Storm <address@hidden> http://www.cua.dk