This is not a simple problem to identify.
Due to a Win7 problem with running 32bit processes on a 64 bit OS the true exception is 'swallowed' which leads to a secondary exception . We have found different problems resulting in the same secondary exception which means different crashes actually all look the same.
Microsoft have posted a work round but it does not work for everybody, yes you guessed, it doesn't work for us. I have been testing it today and get different random crashes so we are worse off.
We are investigating alternative methods of getting to the route cause of this resolution problem which may mean providing a debug version of the application which will be able to show the primary as well as the secondary exception.
Due to a Win7 problem with running 32bit processes on a 64 bit OS the true exception is 'swallowed' which leads to a secondary exception . We have found different problems resulting in the same secondary exception which means different crashes actually all look the same.
Microsoft have posted a work round but it does not work for everybody, yes you guessed, it doesn't work for us. I have been testing it today and get different random crashes so we are worse off.
We are investigating alternative methods of getting to the route cause of this resolution problem which may mean providing a debug version of the application which will be able to show the primary as well as the secondary exception.
Comment