Worst Exception!!

[Member 4608898]

1. Something went wrong but I'm not telling you what 2) Illegal/invalid value but I'm not going to tell you what the illegal/invalid value is.

[Eric_M]

AppHangB...does anyone have any idea where that comes from or what causes it.

[RafagaX]

java.lang.ClassNotFoundException

In an applet, pure bliss to solve... :rolleyes:

CEO at: - Rafaga Systems - Para Facturas - Modern Components for the moment...

[Alan Balkany]

You beat me to it!

[KP Lee]

Both of those exceptions explain what you did and that it is your (the developer's) fault that it happened. If both of them said "You are an effing idiot!", the statement would be true, but not at all helpful about what went wrong. I've worked in languages where you'd never get the first error because there is no such thing as an object and over-indexing an array isn't an error. I've had scheduled programs that blew up because it had an illegal divide by zero error or illegal instruction. Couldn't for the life of me find out what was wrong with my code. Turned out it was scheduled to run when another code was also running that overindexed its array and rewrote my code's machine language in memory and so my code went crazy. The operator happened to notice other people's code were blowing up whenever this same program ran.

Jacquers wrote:

index is outside the bounds of the array

Is a life-saver. Or at least a time-saver because my time isn't wasted when someone else is the idiot. As it is, too many times, that's my role. (IE Idiot programmer.)

[KP Lee]

English is my first language and I didn't get it. That or my memory had a stack-overflow problem so I forgot what you meant. I think my memory is on RAM that doesn't get refreshed too often, I forget what I'm

[AlphaDeltaTheta]

All C compilers are probably like that... even MINGW and MSVC does this till today... By far, only tcc gives good compile time errors!!

[AlphaDeltaTheta]

Hoa! :omg: Well I never programmed any of OS/* or COBOL... But this one looks insane

[AlphaDeltaTheta]

This happened quite often to me, once I had written a file finder program. During tests, once I tried to search a really huge directory tree and boom! Stack Overflow. And that is still in my code -- Known Issues - "WONTFIX" - Craches with huge file trees!

[AlphaDeltaTheta]

Not only .NET. It also happens with native exe's. Mostly if there is an error in the application manifest. (Not the .NET assembly manifest, the one embedded in the exe)

[AlphaDeltaTheta]

My keyboard (PS/2) was plugged in already... what else shall I do?? That time my head grows hot and ":mad: Mr COMPUTER, HOW MANY DAMN KEYBOARDS DO YOU WANT??"

[AlphaDeltaTheta]

patbob wrote:

Check into sxstrace. It generates a log of all side-by-side library loads, reporting what library versions were checked and which were loaded (or not found). Totally useless for C# though, but useful for native code.

Hey, It will be very helpful to me if you please instruct me how to use that tool ??

[AlphaDeltaTheta]

How in the world I'll press F1 after keyboard error??

[AlphaDeltaTheta]

KLSmith wrote:

The service failed to start. Reason: The service finished successfully.

This is a good one... Also in my event log!

[AlphaDeltaTheta]

I have a top-level exception (well, throwable) catcher that catches all these and creates another, Unexpected Error :laugh:

[KP Lee]

Tomz_KV wrote:

This exception message is not useful at all. It would be nice if it gives the object name.

It would be nice if the computer served up tea and crumpets while it explained the vagaries of the code that put it in this situation, but the fact of the matter is that this is a normal unhandled exception message. It is your responsibility as a developer to throw explanatory errors to the system before general purpose messages crumple it up into a general purpose error message. It should at least give you the stack trace, which tells you where the error occurred and if you read that line, it tells you the object it thought it was when the error occurred and you might even find out what the object really was when it was created if you follow the trace far enough. All general purpose error messages are an indication that the developer lacked the caring needed to create meaningful error messages in the special situation it was brought to, completely by (the lack of caring by) the developer's hand.

[Peter Webb]

The temptation is to wrap my entire runnable in something like: Try {// running my program} Catch (Throwable anything) { // act like nothing bad happened and restart somewhere nice } But my head tells me that handling every possible throwable in my code is probably not a great idea.

[dpminusa]

What about the ones with no description and just an error code. You can get some general information from MSDN that leads to a category but ...

"Courtesy is the product of a mature, disciplined mind ... ridicule is lack of the same - DPM"

[BobJanova]

There's actually a really good reason for that, too. If it were an Exception, you'd catch it and try to run some more code, which would almost certainly not have the memory to run, throwing it again. Unexpected exceptions in catch/finally blocks can really screw your code up, so OOME is not supposed to be caught except in the explicit case that you really want to handle it. In Java there's very little you can do about it because you don't directly control your memory.

[BobJanova]

Socket error handling is a nightmare even in a real language/environment ... SocketDisposedException is the .Net equivalent of this, when a socket is closed but it hasn't got around to telling you until you try to write to it.