Hard Light Productions Forums

Off-Topic Discussion => Programming => Topic started by: blackhole on March 30, 2009, 04:01:07 pm

Title: Infuriating Windows 7 Glitch
Post by: blackhole on March 30, 2009, 04:01:07 pm
If you exit the following program before entering a value and hitting enter, the process locks up.

Code: [Select]
#include <iostream>

using namespace std;

int main()
{
  //BSSDEBUG debugger;

  char buf[128];
  cout << "Enter number of iterations: ";
  cin >> buf;
  return 0;
}
Attempting to end the process, however, is futile, since the infinite loop has occured in csrss.exe, a critical system process. If you attempt to end this process, your computer BSODs.

This is SO ****ING ANNOYING

Just FYI.
Title: Re: Infuriating Windows 7 Glitch
Post by: The E on March 30, 2009, 04:04:34 pm
Wait, what? Aborting a program on the command line results in the system locking up? WTF?
Title: Re: Infuriating Windows 7 Glitch
Post by: blackhole on March 30, 2009, 04:21:11 pm
Quote from: The E on March 30, 2009, 04:04:34 pm
Wait, what? Aborting a program on the command line results in the system locking up? WTF?

It does it without fail, much to my chagrin. I can keep running as long as I only make the mistake once, like right now I've got a lovely csrss.exe sucking up one of my cores, but if I do it again, total system lockup.

I hate my job sometimes.
Title: Re: Infuriating Windows 7 Glitch
Post by: The E on March 30, 2009, 04:24:51 pm
Strange, that. I mean, I have a h264-encoder that lives on the command line, and aborting it has never produced the results you described. Maybe there's something wrong with Win7's interactive input handling?
Title: Re: Infuriating Windows 7 Glitch
Post by: blackhole on March 30, 2009, 04:56:17 pm
Quote from: The E on March 30, 2009, 04:24:51 pm
Strange, that. I mean, I have a h264-encoder that lives on the command line, and aborting it has never produced the results you described. Maybe there's something wrong with Win7's interactive input handling?

I've had hundreds of command line applications that have never produced the results I've gotten, until I started up my first command line app ever since i moved to windows 7.