Release build inconsistant behaviour

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

We distributed an VS6 "C" executable.(Built on WIN2K with release mode.)
Surprisingly we are finding runtime errors for q workflow on all XP m/c and
some of the WIN2K systems.All the WIN2K pcs we used for testing never shown
any such error.
If you have any idea of this strange bahaviour.Please let me know.Appretiate
your help in advance.
(NOTE: On XP when it throws runtime error,I am able to track the root
cause,I am keen to know why is it hidden on WIN2K OS)
 
We distributed an VS6 "C" executable.(Built on WIN2K with release mode.)

What else did you install with it? Have you installed the (correct)
versions of any DLLs your program depends on?
Surprisingly we are finding runtime errors for q workflow on all XP m/c and
some of the WIN2K systems.
Click to expand...

Have a look at "Common Problems Switching from Debug to Release Build"
in your VC++ help.

If those don't help you'll need to debug your release version to
locate the cause - see "Turn on Generation of Debug Information for
the Release Build" in your VC++ help.

Dave
 
Dave
First thanks a lot for your valuable inputs.I am not using any dlls, mine
is plain C application built on Visul studio 6 with release version.Whats
driving me nuts is the same executable runs fine on WIN2K,but throws run time
error alwasys on XP for some workflows/steps.
Can anyone help me whats this missing link...
thanks
sam
 
First thanks a lot for your valuable inputs.I am not using any dlls, mine
is plain C application built on Visul studio 6 with release version.
Click to expand...

Presumably you're using some 'C' run-time functions, so are you
statically linking the run-time? Have you checked your dependencies
using the Depends utility (http://www.dependencywalker.com/)?
Whats
driving me nuts is the same executable runs fine on WIN2K,but throws run time
error alwasys on XP for some workflows/steps.
Click to expand...

As I mentioned, try debugging your release build (on the machine where
the problem occurs).

Dave
 
(NOTE: On XP when it throws runtime error,I am able to track the root
cause,I am keen to know why is it hidden on WIN2K OS)
Click to expand...

What was the reason of the problem on XP? If you share it with us,
it will be much easier to explain why it was not reproducible on Win2K.

Regards,
Oleg
 
Back
Top