Worst Exception!!
-
"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.
YvesDaoust wrote:
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
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.
We can program with only 1's, but if all you've got are zeros, you've got nothing.
-
What's in your mind is the worst exception in programming?? My favourite is Out of Memory!
I would like to submit the following from [^]:
Three things are certain: Death, taxes, and lost data. Guess which has occurred. Everything is gone; Your life's work has been destroyed. Squeeze trigger (yes/no)? I'm sorry, there's -- um -- insufficient -- what's-it-called? The term eludes me ... Windows NT crashed. I am the Blue Screen of Death. No one hears your screams. Seeing my great fault Through darkening blue windows I begin again The code was willing, It considered your request, But the chips were weak. Printer not ready. Could be a fatal error. Have a pen handy? A file that big? It might be very useful. But now it is gone. Errors have occurred. We won't tell you where or why. Lazy programmers. Server's poor response Not quick enough for browser. Timed out, plum blossom. Chaos reigns within. Reflect, repent, and reboot. Order shall return. Login incorrect. Only perfect spellers may enter this system. This site has been moved. We'd tell you where, but then we'd have to delete you. wind catches lily scatt'ring petals to the wind: segmentation fault ABORTED effort: Close all that you have. You ask way too much. First snow, then silence. This thousand dollar screen dies so beautifully. With searching comes loss and the presence of absence: "My Novel" not found. The Tao that is seen Is not the true Tao, until You bring fresh toner. The Web site you seek cannot be located but endless others exist Stay the patient course Of little worth is your ire The network is downAnd many others.
Gus Gustafson
-
What's in your mind is the worst exception in programming?? My favourite is Out of Memory!
-
What's in your mind is the worst exception in programming?? My favourite is Out of Memory!
- 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.
-
What's in your mind is the worst exception in programming?? My favourite is Out of Memory!
-
What's in your mind is the worst exception in programming?? My favourite is Out of Memory!
java.lang.ClassNotFoundException
In an applet, pure bliss to solve... :rolleyes:
CEO at: - Rafaga Systems - Para Facturas - Modern Components for the moment...
-
All of the "something went wrong, but I'm not going to tell you what, why, or even where, neener neener"-Exceptions. XNA was pretty good at throwing those - often in a manner that the debugger would fail to run. Actually native code in general is good at that. For example, if anything happens after the stack gets misaligned on win64, things go very wrong.
You beat me to it!
-
object reference not set to an instance of an object index is outside the bounds of the array
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.)
-
The fact you commented, says you did. Obviously, you and I are more subtle than the others. :-D
I was brought up to respect my elders. I don't respect many people nowadays.
CodeStash - Online Snippet Management | My blog | MoXAML PowerToys | Mole 2010 - debugging made easier -
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.
All C compilers are probably like that... even MINGW and MSVC does this till today... By far, only tcc gives good compile time errors!!
-
<shudder> I'd forgotten that one: OS/360 in my case. And wasn't the explanation helpfull as well? "The RTM2WA is pointed to by the TCB of the failing task (field TCBRTWA), and is listed after the abnormally ending TCB." Why can't you just say "You forgot a comma you idiot" and let us both move on? :laugh:
The universe is composed of electrons, neutrons, protons and......morons. (ThePhantomUpvoter)
Hoa! :omg: Well I never programmed any of OS/* or COBOL... But this one looks insane
-
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.
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!
-
"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.
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)
-
That is so you fix the problem (i.e. plug in a keyboard) before trying to use the computer.
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??"
-
YvesDaoust wrote:
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
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.
We can program with only 1's, but if all you've got are zeros, you've got nothing.
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 ??
-
How in the world I'll press F1 after keyboard error??
-
Seems to me that worst is being interpreted as either: nonsensical, useless (programmer too lazy to write a meaningful message), or a dreaded message, where something bad really did happen. Here is a nonsensical one: One recent message in my Windows-7 system event log was The service failed to start. Reason: The service finished successfully.
KLSmith wrote:
The service failed to start. Reason: The service finished successfully.
This is a good one... Also in my event log!
-
Up until yesterday "Out of Memory" was my worst exception. By coincidence, today I found out was not actually an exception, but an error condition in Java, which explains why I wasn't catching it. So now its been promoted to worst throwable. And I hate pretty much everything you can throw.
I have a top-level exception (well, throwable) catcher that catches all these and creates another, Unexpected Error :laugh:
-
Jacquers wrote:
object reference not set to an instance of an object
This exception message is not useful at all. It would be nice if it gives the object name.
TOMZ_KV
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.
-
I have a top-level exception (well, throwable) catcher that catches all these and creates another, Unexpected Error :laugh:
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.
