Worst Exception!!

[Lost User]

And everything we wrote that long ago was better? :)

Sent from my BatComputer via HAL 9000 and M5

[pkfox]

Wonderful stuff !!!

When the going gets weird the weird turn pro - Hunter S Thompson RIP

[pkfox]

Ah yes the compiler messages of MicroFocus COBOL !!! - miss one full-stop (period) and you would get 1000's of errors. Deep joy.

When the going gets weird the weird turn pro - Hunter S Thompson RIP

[Joezer BH]

Quote:

"Error: Cannot delete 6342_637.oft, there is not enough disk space. Delete one or more files to free disk space, and then try again."

Never underestimate the difference you can make in the lives of others.

[OriginalGriff]

Well, I at least tried to tell the user what he had done wrong. Most of the time. Some of the time, probably. But MS didn't even give a nod towards "user friendly" in those days; it was "user hostile" at best, and "outright hatred" at worst.

The universe is composed of electrons, neutrons, protons and......morons. (ThePhantomUpvoter)

[OriginalGriff]

Oh god, I'd forgotten that piece of zen wonderfulnes

The universe is composed of electrons, neutrons, protons and......morons. (ThePhantomUpvoter)

[Joezer BH]

Not an exception but with the same flavour. During windows start-up device detection: "Keyboard error or no keyboard present." and below the well known "Press F1 to continue or ESC to enter SETUP."

Never underestimate the difference you can make in the lives of others.

[Gary R Wheeler]

0xC0000005, aka Windows access violation. Detection is nowhere near the place in your source code that caused the problem, and the actual cause usually has nothing to do with an attempt to access any kind of protected object.

Software Zen: delete this;

[Joezer BH]

Oh, just remembered another one: "<unknown> had detected an error in <unknown>, <unknown> will now close."

Never underestimate the difference you can make in the lives of others.

[Lost User]

Gary R. Wheeler wrote:

Windows access violation.

Access is a violation of many things and deserves its own exception. ;)

Sent from my BatComputer via HAL 9000 and M5

[PIEBALDconsult]

When things go wrong, even the worst exception is better than no exception. :sigh:

[AlphaDeltaTheta]

Well this is the one I was always facing in my old Celeron box

[AlphaDeltaTheta]

In good old days of native c++... now I have moved to managed, atleast the debugger gives me some stack traces... I never learnt how to debug a native app!

[JeremyBob]

Agreed, the Access Violation errors are the absolute worst.

[YvesDaoust]

"the application has failed to start because its side-by-side configuration is incorrect" This one gives me nightmares because so far I have been unable to troubleshoot it. The application refuses to start, that's it. No clue on what DLL was missing/of invalid type or whatsoever. Quite efficiently contributes to the arcane mysteries of .NET technology. One more instance of what harold aptroot said.

[base2 codeproject]

Stack overflow exceptions! Although they don't happen often, they are tricky to debug as the stack trace isn't available to me when it happens.

[Farlop]

SQL Server: "String or binary data would be truncated" which column? "aaaaah i'm not telling you!!" Drives me mad every time!

[hollysong]

Multiple-step operation generated errors. Check each status value.

[BobJanova]

The Zortech C compiler was a bit like that with any syntax mistake (like missing a semicolon or for sure a brace): look at the first error and ignore the other 200 it generated.

[Sander Rossel]

There are quite some Exceptions I really don't like... NullReference, String or binary data would be truncated, that sort of stuff. Mostly because the error doesn't indicate what was null or what data would be truncated. But the worst of them all, mostly because I've seen it not handled correctly way to often, See the inner Exception for details... Ok, so where is that inner exception? Not in some logging, not in some message box, actually it is nowhere! The programmer programming this code did not ever stop to think about the fact that an Exception may have an inner exception. Good luck finding out what's wrong... :sigh: Now comes the fun part. I fixed it and the first Exception I got had an inner exception in the inner exception... Luckily I log exceptions recursively for these cases :)

It's an OO world.

public class Naerling : Lazy<Person>{
public void DoWork(){ throw new NotImplementedException(); }
}