Re: rogue process maxing cpu and unresponsive to signals

> There's a lot of parts of the code that don't check for signals,
> because normally they don't run for any real length of time... until
> they do. :) The factorial calculation is an example that was recently
> fixed. So it's possible that something in your query is in that same
> condition. You may be stuck with a kill -9, but it would be good to
> identify what part of the code is hung up so we can determine if it
> makes sense to add signal handling.

Yeah, if there's any information I can furnish that would help determine
where it's getting stuck, let me know. I'm not really sure how to gain
any visibility into what the process is doing at this point.

Jon