Wonderful description strings!
-
I was working with some old code (well, as usual) and came across this situation where the debugger reported an unhandled exception. I handled it, and well...
try
{
//existing code which was not within the try block
}
catch(CPrException *pExc)
{
OutputDebugString(pExc->GetErrorDescription());
delete pExc;
}And error description printed in the external debugger was:
Something is really wrong!
:wtf: Something is wrong? Really wrong? Well, thanks for letting me know. Someone out there was having a really wicked sense of humor while writing it. I would personally want to take him out and beat him to death with an old-skool mechanical keyboard.
It is a crappy thing, but it's life -^ Carlo Pallini
-
I was working with some old code (well, as usual) and came across this situation where the debugger reported an unhandled exception. I handled it, and well...
try
{
//existing code which was not within the try block
}
catch(CPrException *pExc)
{
OutputDebugString(pExc->GetErrorDescription());
delete pExc;
}And error description printed in the external debugger was:
Something is really wrong!
:wtf: Something is wrong? Really wrong? Well, thanks for letting me know. Someone out there was having a really wicked sense of humor while writing it. I would personally want to take him out and beat him to death with an old-skool mechanical keyboard.
It is a crappy thing, but it's life -^ Carlo Pallini
I have adopted also some code from vb. This code logs on customer machines to the windows eventlogger. The log will only tell me: "Invalid operation. Call you system administrator" There is no error code. No trace where the hell it is going wrong. So they call me. I work here 2 years now and the original developer left 1 year ago. Ofcourse now i get the error messages. All i am saying, i know your pain!
-
I was working with some old code (well, as usual) and came across this situation where the debugger reported an unhandled exception. I handled it, and well...
try
{
//existing code which was not within the try block
}
catch(CPrException *pExc)
{
OutputDebugString(pExc->GetErrorDescription());
delete pExc;
}And error description printed in the external debugger was:
Something is really wrong!
:wtf: Something is wrong? Really wrong? Well, thanks for letting me know. Someone out there was having a really wicked sense of humor while writing it. I would personally want to take him out and beat him to death with an old-skool mechanical keyboard.
It is a crappy thing, but it's life -^ Carlo Pallini
Something was really wrong, with the original coder!
-
Something was really wrong, with the original coder!
I'll second that - LOL :D
GSoC 2009 student for SMW! --- My little forums: http://code.bn2vs.com --- 70 72 6F 67 72 61 6D 6D 69 6E 67 20 34 20 6C 69 66 65!
-
I was working with some old code (well, as usual) and came across this situation where the debugger reported an unhandled exception. I handled it, and well...
try
{
//existing code which was not within the try block
}
catch(CPrException *pExc)
{
OutputDebugString(pExc->GetErrorDescription());
delete pExc;
}And error description printed in the external debugger was:
Something is really wrong!
:wtf: Something is wrong? Really wrong? Well, thanks for letting me know. Someone out there was having a really wicked sense of humor while writing it. I would personally want to take him out and beat him to death with an old-skool mechanical keyboard.
It is a crappy thing, but it's life -^ Carlo Pallini
Having been there myself many times I understand that at crunch time error messages get minimal consideration. But if there is time to write "Something is really wrong!" surely there is time to write an error message that is a wee bit more helpful. :| Bill W
Just because the code works, it doesn't mean that it is good code.