Deliberate Crash
-
Once back in the early 90s when internet connections were not so common. I was working on some general exception trapping in an application written in C, to test it I added something like this to startup code of the application
int* ptrDummy = NULL;
if (*ptrDummy == 0) /* this causes an access violation*/Having finished that I checked it in to the main product code which got build into a special release for a customer who had had some problems with the software. An engineer was sent from our office in the uk to the customer in the South of France with the software on a CD. The engineer then installed it on the customers system, ran it up in frount of the customer only to discover that it crashed on startup. Sorry engineer.
-
Once back in the early 90s when internet connections were not so common. I was working on some general exception trapping in an application written in C, to test it I added something like this to startup code of the application
int* ptrDummy = NULL;
if (*ptrDummy == 0) /* this causes an access violation*/Having finished that I checked it in to the main product code which got build into a special release for a customer who had had some problems with the software. An engineer was sent from our office in the uk to the customer in the South of France with the software on a CD. The engineer then installed it on the customers system, ran it up in frount of the customer only to discover that it crashed on startup. Sorry engineer.
That's why you should always surround this type of test code with a safety that requires some sort of deliberate configuration change to trigger. I wish I could have learned this before I managed to release an installer with test diagnostic dialogs embedded in it. While our QA team was never able to reproduce the steps needed to trigger things, the customers sure could. :(
-
That's why you should always surround this type of test code with a safety that requires some sort of deliberate configuration change to trigger. I wish I could have learned this before I managed to release an installer with test diagnostic dialogs embedded in it. While our QA team was never able to reproduce the steps needed to trigger things, the customers sure could. :(
-
-
Once back in the early 90s when internet connections were not so common. I was working on some general exception trapping in an application written in C, to test it I added something like this to startup code of the application
int* ptrDummy = NULL;
if (*ptrDummy == 0) /* this causes an access violation*/Having finished that I checked it in to the main product code which got build into a special release for a customer who had had some problems with the software. An engineer was sent from our office in the uk to the customer in the South of France with the software on a CD. The engineer then installed it on the customers system, ran it up in frount of the customer only to discover that it crashed on startup. Sorry engineer.
-
Once back in the early 90s when internet connections were not so common. I was working on some general exception trapping in an application written in C, to test it I added something like this to startup code of the application
int* ptrDummy = NULL;
if (*ptrDummy == 0) /* this causes an access violation*/Having finished that I checked it in to the main product code which got build into a special release for a customer who had had some problems with the software. An engineer was sent from our office in the uk to the customer in the South of France with the software on a CD. The engineer then installed it on the customers system, ran it up in frount of the customer only to discover that it crashed on startup. Sorry engineer.
Shouldn't you be telling this to a priest in a confessional booth?
Steve Wellens
-
Once back in the early 90s when internet connections were not so common. I was working on some general exception trapping in an application written in C, to test it I added something like this to startup code of the application
int* ptrDummy = NULL;
if (*ptrDummy == 0) /* this causes an access violation*/Having finished that I checked it in to the main product code which got build into a special release for a customer who had had some problems with the software. An engineer was sent from our office in the uk to the customer in the South of France with the software on a CD. The engineer then installed it on the customers system, ran it up in frount of the customer only to discover that it crashed on startup. Sorry engineer.
In most cases when see code that can catch an access violation your looking at a coding horror.
Steve
-
Shouldn't you be telling this to a priest in a confessional booth?
Steve Wellens
-
In most cases when see code that can catch an access violation your looking at a coding horror.
Steve