What?
I am 99.99% sure it used to interrupt the GUI process if no other viable 
candidate could be found, why change that?
At least in my mind, if you hit cmd - dot, either you want to interrupt some 
process blocking the UI on a higher priority, or you want the UI process itself.
For everything else, there's the Process Browser.

Cheers,
Henry

On May 1, 2013, at 2:31 AM, Igor Stasenko wrote:

> On 30 April 2013 22:44, Stéphane Ducasse <stephane.duca...@inria.fr> wrote:
>> trying to publish a slice on my harddisc without network….
>> and I could not interrupt anything.
>> No cmd+. no interdiction sign did anything :(
>> 
>> So is it normal?
>> Not being able to interrupt something is a pain.
>> 
>> stef
> 
> the problem stems from the point that when you press cmd+.
> an interrupt process logic looking for some other active process
> to stop it..
> now since UI process blocked by semaphore, as well as rest,
> it finds nothing to interrupt and ignores it :)
> 
> i think we should think about it, like putting synthesized context
> with '1halt', to UI process, so when it will awake, it will be halted.
> 
> Or... if interrupt handler found nothing,  then always spawn new UI process
> opening debugger on old one.
> 
> -- 
> Best regards,
> Igor Stasenko.
> 


Reply via email to