Re: Behavior of Ctrl+C with respect to unwind_protect_cleanup blocks

[Rik]

On 06/10/2017 07:04 AM, John W. Eaton wrote:
> On 06/10/2017 09:33 AM, Rik wrote:
>
>> Between versions 4.0 and 4.2 the behavior of unwind_protect blocks with
>> respect to Ctrl+C interrupts changed.  Previously, an interrupt was treated
>> the same as an error and the unwind_protect_cleanup block was executed.
>> Now, the interrupt is immediate and returns control to the command prompt
>> without taking any other actions.
>
> I don't think any change like that was intentional.  Do we know what
> changeset is responsible?

Bisecting, as usual, was not as straightforward as it should have been. 
However, I did finally locate the responsible changeset.

parent: 20651:b70cc4bd8109
 begin removal of global error_state variable

--Rik