In article <7lgiq3$nv3$1@nnrp1.deja.com>,
deja_ljg@my-deja.com wrote:
> In article <7lec9j$uhr$1@nnrp1.deja.com>,
> Tom Williams wrote:
> > In article <7ldrph$ns3$1@nnrp1.deja.com>,
> > deja_ljg@my-deja.com wrote:
> > > I have created a stand-alone CVI
application that
> > > worked fine in CVI 5.0 but when migrated and
> > > rebuilt in CVI 5.0.1, it will not launch
> > > correctly. It exits with a code of -1. Has
> > > anyone else had this problem? Any
suggestions?
> > >
> > > (I've tried increasing the stacksize
already and
> > > it does no good)
> > >
> > > Sent via Deja.com http://www.deja.com/
> > > Share what you know. Learn what you don't.
> > >
> >
> > Does it run in the CVI 5.0.1 environment (not
as a standal
one
> > executable)?
>
> Yes, it does work in CVI 5.0.1 ( not as a
standalone )
>
If you have a variable declared globally in one
module which is explicitly initialized where it
is declared then later change that variable in
that same module and then reference it via extern
in another module it will generally ONLY show the
initial value. This is ONLY true when running a
standalone executable! If you have something
dependent on proper behavior then this could be
the problem. printf debugging found this one for
me.
module1.c
int a = 5;
....
a = 7;
end of module1.c
module2.c
extern int a;
// whats the value of a even after
// the a=7 has executed in module1.c??
// In a standalone .exe it will probably
// still be 5!!!
end of module2.c
Sent via Deja.com http://www.deja.com/
Share what you know. Learn what you don't.
