R
rdspicer
Hi
I have a probelm with a simulation I am running and I was hoping
someone out there may be able to shed some light on the subject.
Before I start, this is what I am using:
MVSC++6.0 (SP6 installed), using 3Ghz Intel machine, Windows Xp, 1.5
Gb SDRAM
This could be a little difficult to explain so please bear with me.
My project is a video encoder that is very big in size and written in C
++.
When I run the sim in Release mode and only when I get to frame 90 do
things start going wrong. However when I run in debug mode, the
projects executes correctly and generates the correct results. Going
back to release mode, I inserted some debugging code (logging
variables to file etc to see if they were in an undefined state etc)
and then the project generated the correct results. So in other words,
only when I was logging specific variables to file in release mode
would the project execute correctly.
Immediately I would think this would be to an uninitialised variable
problem however why is the problem only apparent after 89 frames worth
of encoding? It seems like I have to force the use of these variables
for them to be used correctly. Am I losing the plot?
I have tried to use BoundsChecker to trap any memory leaks and pointer
problems, however because the project is so big and under normal
conditions is so slow to execute, BoundsChecker seems to grid to a
halt and never gets anywhere!
Any suggestions on what else to consider or how to trap this little
nasty?
Many thanks
Ryan
I have a probelm with a simulation I am running and I was hoping
someone out there may be able to shed some light on the subject.
Before I start, this is what I am using:
MVSC++6.0 (SP6 installed), using 3Ghz Intel machine, Windows Xp, 1.5
Gb SDRAM
This could be a little difficult to explain so please bear with me.
My project is a video encoder that is very big in size and written in C
++.
When I run the sim in Release mode and only when I get to frame 90 do
things start going wrong. However when I run in debug mode, the
projects executes correctly and generates the correct results. Going
back to release mode, I inserted some debugging code (logging
variables to file etc to see if they were in an undefined state etc)
and then the project generated the correct results. So in other words,
only when I was logging specific variables to file in release mode
would the project execute correctly.
Immediately I would think this would be to an uninitialised variable
problem however why is the problem only apparent after 89 frames worth
of encoding? It seems like I have to force the use of these variables
for them to be used correctly. Am I losing the plot?
I have tried to use BoundsChecker to trap any memory leaks and pointer
problems, however because the project is so big and under normal
conditions is so slow to execute, BoundsChecker seems to grid to a
halt and never gets anywhere!
Any suggestions on what else to consider or how to trap this little
nasty?
Many thanks
Ryan