in reply to Tracing or ignoring SIGQUIT and SIGINT

I think you need to figure out where these signals are coming from. You aren't doing it. No other user is doing it. So who else could it be? I suspect that a virus scanner or some sort of "Windows firewall" program (eg, service in Windows world, daemon in Unix world) is figuring out that you are alive and trying to stop you.

Basically somebody else on this Windows platform is unhappy that you are running and is actively trying to kill you. I found this audio/visual clip on the net and it sounds cool. I watched a bit of it, enough to recommend that you watch it if you don't know about Windows Services. http://www.jasonn.com/turning_off_unnecessary_services_on_windows_xp Basically watch this video to get an idea of how to mess with Window's services, roll in there and turn off everything that you can while still allowing your program to run. Then re-enable things until your program stops.

But my guess is that one of the anti-virus or firewall things that doesn't know about your program is trying to stop it especially if it is trying to communicate on the web. The number of possibilities is so vast, that I can't offer specifics. But you will have to find that program and then figure out how to get it to "trust you".

Anyway, the MS OS is not doing this, some other program is. You don't want to ignore these signals (although I can post the code so that you can) because you want to (or should want to) be "well behaved" in the Windows environment.

Sorry that this doesn't wind up at a thing like: set parmXYZ to 23! You are in for some hacking. I wish you well and I hope I got you started!

  • Comment on Re: Tracing or ignoring SIGQUIT and SIGINT