Mmm, it's not that easy ... the whole thing is something like a
standalone agent consisting of a main prog
which loads various libs, config, data, ... then it instantiates an
embedded Clips engine, reads Clips code etc.
The pure Clips files will not help because we also define a set of
UserFunctions which are required.
What I can do is to build a debuggable Installer with everything
inside - this reflects what we are using and where
we experience the problem. This also includes all the Clips files,
plus I could add an archive with the Clips sources as being used (I
don't expect you to look through them :-) but rather to make sure they
match the executable code).
Alternatively (even easier) we could give you access to our dev/test
system (via OpenVPN + Remote Desktop)
What do you think?
Many thx in advance!!
tge
PS: Btw, I also let the whole thing run through valgrind (on Linux)
and purify (we have on Windows32 only :-|) - nothing.
PS2: I also spent quite some times searching through discussions
related to Windows topics such as mixing debug and non-debug code
which originally caused major troubles, but the exact same problem
appears in debug as well as in pure non-debug code. Therefore I guess
we can exclude this too.