Codephrase causing system crash?, page 1

posted on May, 4 2005 @ 07:51 AM

link

the computer code has to balance out or it wouldnt be a balanced equation. is there a certain code or phrase you can input or type that the computer cant balance?

kenshiro2012

posted on May, 4 2005 @ 07:54 AM

link

not quite sure what you are geting at.
To quote the old computer geek adage "garbage in = garbage out"
A conputer can only work with the informaiton that is inputed in to it.
Ow, wait a minute, are you shooting for something like having a computer find the last interger of PI?

Byrd

posted on May, 4 2005 @ 10:09 AM

link

Speaking on behalf of all of us who make our living writing code.....

................NO..............

C'mon -- we're not that stupid. Anyone who wrote code that was THAT fragile would be out the door as soon as the quality control folks got their mitts on it. Our salaries rely on us writing code that does NOT crash.

And unless you're dealing with a tiny company, whole teams of programmers work on software... not just one person. After they're done, the quality control checkers get it and then the beta testers. And then the public.

Yes, you can crash individual programs if the code doesn't have good error checking and those can crash the system. Yes, badly written software and web pages can be victimized by buffer overlfow exploits (but you have to give the command at the right point.)

Yes, there are hacks and tweaks. If you know the correct commands, you can use DEBUG to initiate the shutdown.

And yes, you could write one if you liked.

But in the industry, if you had a codeword that caused a crash, you would be out the door so fast your head would spin, and you'd have lawyers snapping at your heels with lawsuits.

RichardPrice

posted on May, 4 2005 @ 04:34 PM

link

Originally posted by Shadow88
the computer code has to balance out or it wouldnt be a balanced equation. is there a certain code or phrase you can input or type that the computer cant balance?

Depends how well the system is coded really. Most applications can be brought down with a divide by zero error, or a buffer overrun. The following code, when compiled and run, can crash most computers:

#include

main() [
for(;

fork();
]

Rather simple eh?

Theres no such thing as a balanced equation in computing. Code does not have to 'balance'.

Oh and Byrd, try the following code in Internet Explorer (save it out into a html file and view it):

<html>
<body>

<form>
<input type crash>
</form>

</body>
</html>

The above control was left in IE by the development team as a test crash case, so they could crash the browser whenever they wanted.

[edit on 4/5/2005 by RichardPrice]

Shadow88

posted on May, 6 2005 @ 11:39 AM

link

okies dudes that all i wanted 2 no. thnx!:p