Kill a handler

[J. Landman Gay]

On 3/30/14, 8:58 AM, Kevin Miller wrote:
> There is an alternative to command-. on Mac which will often, though not
> always rescue you when you¹re deep in handler stack you can¹t break out of.
>
> Get the process ID from Activity Monitor. Then run:
>
> kill -sighup processID
>
>
> E.g. if LC has PID 9382:
>
> kill -sighup 9382

Thanks for this. I just looked it up and apparently this command just 
attempts to reset the app without killing it entirely. I'm certainly 
going to try it the next time the IDE gets into one of its loops while 
debugging.

Larry: I was assuming your hangs happen during run time, which I almost 
never see. But I do see them occasionally while stepping through the 
debugger, and it's most ofen caused by the background IDE scripts 
getting into a loop. If this terminal command can break out of those 
situations then it's a very welcome thing to know.

It's my understanding that eventually RR would like to disassociate the 
IDE scripts from our own so that these loops won't affect our work. 
That's probably a ways off, but it will be good when it happens.

-- 
Jacqueline Landman Gay         |     jacque at hyperactivesw.com
HyperActive Software           |     http://www.hyperactivesw.com