Problem only in release version

B

babak

Hi everybody
I'm working with a project in embedded Visual Studio 4 and I have a
general problem which I hope that somebody can help me with. My problem
is the following:
My project works fine in debug version but behaves strangely and
sometimes crashes when I run it in release version. I suspect that it
is some sort of memory problem but it is not that easy to find out what
the problem exactly is (the project is rather big with maybe 30000
lines of code).
It should be the same code that runs in the both versions, right? Or is
there some part of the code in a project that might differ in debug and
release version?

Thanks for all your help.
Regards.
/Babak
 
C

Carlos J. Quintero [VB MVP]

I'm working with a project in embedded Visual Studio 4
and I have a general problem which I hope that somebody can help me with.
My problem is the following:
My project works fine in debug version but behaves strangely and
sometimes crashes when I run it in release version. I suspect that it
is some sort of memory problem but it is not that easy to find out what
the problem exactly is (the project is rather big with maybe 30000
lines of code).
It should be the same code that runs in the both versions, right? Or is
there some part of the code in a project that might differ in debug and
release version?

The Release configuration may perform some optimizations that can cause a
different behaviour. Since the settings of each configuration (Debug /
Release) are configurable, I would suggest to create a 3rd configuration
copying it from Release and start changing settings towards the Debug
configuration. At some point the app will stop crashing and the last changed
setting can tell more about the problem.


--

Best regards,

Carlos J. Quintero

MZ-Tools: Productivity add-ins for Visual Studio .NET, VB6, VB5 and VBA
You can code, design and document much faster.
Free resources for add-in developers:
http://www.mztools.com
 
B

babak

Carlos J. Quintero [VB MVP] skrev:
The Release configuration may perform some optimizations that can cause a
different behaviour. Since the settings of each configuration (Debug /
Release) are configurable, I would suggest to create a 3rd configuration
copying it from Release and start changing settings towards the Debug
configuration. At some point the app will stop crashing and the last changed
setting can tell more about the problem.


--

Best regards,

Carlos J. Quintero

Hi Carlos
Thanks for your reply. I will try your suggestion and hopefully that
will give me some ideas of what might be wrong.

/Babak
 
N

Nick Z.

Also, this might be obvious, but I'll say it just in case.

You may have code that is marked to be included only in the debug version.

It could look like this for example.

public void SomeFunc()
{
//do stuff
//...

#if DEBUG
//do something only in the debug version
#endif

//do the rest of it
}

Just a thought, hope this helps,
Nick Z.
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top