The worst error message ever, ever
-
When I was at college i was forced to make a project with lazarus(a free Delphi IDE), Thi IDE is so wrong at so many levels that among other stuff that happened to me i received this error messsage "Oops the IDE has entered in depuration state(the ide freezed down) you only have to close it and wait for the worse"
I remember reading about a program someone was debugging with message boxes, and he made them all tsundere, to ease the tedium. Sadly, he shipped it without removing all of the messages. 2 weeks later, he dealt with a phonecall from a client who quoted: "I-It's not like I wanted to give you data, desuwa~, I just made to much!"
-
When I was at college i was forced to make a project with lazarus(a free Delphi IDE), Thi IDE is so wrong at so many levels that among other stuff that happened to me i received this error messsage "Oops the IDE has entered in depuration state(the ide freezed down) you only have to close it and wait for the worse"
I was pushing the limits of an algorithm to find the limit of it's recursive processing. Then I put in a try/catch to gently and safely bring the app down when it failed. This isn't a bad error message, it's a failure in expectations. When it blew, it was supposed to write a formatted message in the catch block. When you get a stack overflow error/message, the app shuts down, no catch processing, no final executions, you're done, you're out. I thought try/catch was supposed to always catch failures.
-
When I was at college i was forced to make a project with lazarus(a free Delphi IDE), Thi IDE is so wrong at so many levels that among other stuff that happened to me i received this error messsage "Oops the IDE has entered in depuration state(the ide freezed down) you only have to close it and wait for the worse"
My personal favorite, encountered only once while trying to open a project file in Borland C++Builder 6, it went something like; "We were unable to process your request. Reason: The window does not have scroll bars." Yup, apparently scroll bars are an essential part of loading the file.
-
MS-DOS also had a "Screen not found" error message, which no one ever saw because it was meant to be displayed on the screen
Yeah, but Windows took that one just one step further... I recall seeing the BSOD on my friend's computer, and I think it was Win95. It just read: "It seems you have not plugged in a monitor. Please plug in a monitor and press a key to continue." In fact, pressing a key wouldn't have done anything, but what has been troubling me for all this years now: HOW did the programmer meant this message - if it's conditions were really met - would be transported to the user? Magic Crystal Ball? Needless to say, _we_ saw the message because there _was_ a monitor plugged in.
That seems to be a PEBKAC problem, Sir. Why don't you go and fetch a coffee while I handle the operation?
-
Delphi 5: "Catastrophic error." in a single message box with a ok button. Simple! Amazing! :))
Might as well have replaced the "ok" with "panic"... :laugh:
-
When I was at college i was forced to make a project with lazarus(a free Delphi IDE), Thi IDE is so wrong at so many levels that among other stuff that happened to me i received this error messsage "Oops the IDE has entered in depuration state(the ide freezed down) you only have to close it and wait for the worse"
I remember a Win 95 message when connecting to a NT4 Server as you try to attach to a share. Something along the lines: "I can't log you in, as you may have already logged off"
-
While a greenie, the following code was (accidentally) released into production: Messagebox: Title "Oops" Message: "Mikel Sucks as a programmer since this should never happen."
-
When I was at college i was forced to make a project with lazarus(a free Delphi IDE), Thi IDE is so wrong at so many levels that among other stuff that happened to me i received this error messsage "Oops the IDE has entered in depuration state(the ide freezed down) you only have to close it and wait for the worse"
-
HA! Good Question. The circumstances were such that it really should have never happened. It was one of those "when a user clicks x and Venus is in retrograde" scenarios. So to answer you question: Once After that, I plugged the logic hole and put a "friendly" error in its place.
-
Some of the latest bad error messages we've seen here are "An unknow error has occurred" (yep, with the spelling mistake) Another From a M$ app logged this useful message to the windows event log "The" I think that's my favorite.