I am seeing a very strange problem as follows...
I have a loop where a fair amount of processing is going on and near
the top of the loop I access a class that has only static helper
functions to perform some calculations. After some number of
iterations, randomly, I'll get an uncaught NullValueExcept ion error on
one of these calls, as if the class name is being treated as an object
reference and is null. Here is some psuedo-code to illustrate:
Object anObject = GetNextObject() ;
while (anObject != null)
{
double a_value = StaticClass.Cal culateA(anObjec t); // !!!
double b_value = StaticClass.Cal culateB(anObjec t);
// Lots of processing
anObject = GetNextObject() ;
}
When I get the exception it is invariably on the first static function
call.
What is truly strange is that this problem will come and go depending
on minor, apparently unrelated changes made near the bottom of the
iteration. For example, simply inserting the statement:
int foo = 150;
where 'foo' is never actually referenced or used anywhere seems to
"fix" the problem. Wrapping the static function calls in a try-block
also seems to "fix" the problem (no exceptions are ever caught -- the
mere presence of the try-catch construct seems to cure the problem).
If I compile for release and run the code outside of the VS.NET
environment there is never any problem.
So..., I'm suspecting some problem either in the debugging code or
running debugging code in the VS.NET environment but really have no
good means to track this down any further. It's not critical since I
seem to have a work-around (I picked the try-catch as opposed to
setting 'foo' to 150 :-) I was just curious whether anyone had
encountered anything similar? Thanks!
-- TB
I have a loop where a fair amount of processing is going on and near
the top of the loop I access a class that has only static helper
functions to perform some calculations. After some number of
iterations, randomly, I'll get an uncaught NullValueExcept ion error on
one of these calls, as if the class name is being treated as an object
reference and is null. Here is some psuedo-code to illustrate:
Object anObject = GetNextObject() ;
while (anObject != null)
{
double a_value = StaticClass.Cal culateA(anObjec t); // !!!
double b_value = StaticClass.Cal culateB(anObjec t);
// Lots of processing
anObject = GetNextObject() ;
}
When I get the exception it is invariably on the first static function
call.
What is truly strange is that this problem will come and go depending
on minor, apparently unrelated changes made near the bottom of the
iteration. For example, simply inserting the statement:
int foo = 150;
where 'foo' is never actually referenced or used anywhere seems to
"fix" the problem. Wrapping the static function calls in a try-block
also seems to "fix" the problem (no exceptions are ever caught -- the
mere presence of the try-catch construct seems to cure the problem).
If I compile for release and run the code outside of the VS.NET
environment there is never any problem.
So..., I'm suspecting some problem either in the debugging code or
running debugging code in the VS.NET environment but really have no
good means to track this down any further. It's not critical since I
seem to have a work-around (I picked the try-catch as opposed to
setting 'foo' to 150 :-) I was just curious whether anyone had
encountered anything similar? Thanks!
-- TB
Comment