[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [TRNSYS-users] CVF6.6



Hi Max,

 

This usually happens when the DLL loaded by TRNSYS is not the one you are currently debugging.

Typically, you re-installed TRNSYS (so it is in release mode) and you compile your .DLL in to .\Uerlib\ DebugDlls.

Or, TRNSYS was in \TRNSYS16 before, now it is under \Program Files\Trnsys16, … CVF recompiles happily to the wrong directory and silently creates it if it does not exist (while Trnsys doesn’t know about it).

 

When you hit F5 in CVF, the CVF Output window lists all Dlls that are loaded. Check if it loads the one you just compile (e.g. look at the path and date, or, better, delete it and check if it is created at the spot where TRNSYS – the one you execute - loads it.).

 

Werner

 


De : Max Werlein [mailto:maxwithhat@hotmail.com]
Envoyé : lundi 19 janvier 2009 17:15
À : trnsys users
Objet : [TRNSYS-users] CVF6.6

 


Dear TRNSYS users,

I have written a type with CVF 6.6. Y could Debug it without any problems before. After reinstalling the computer, I installed both TRNSYS and CVF again implemented my typs, and the simulations run without a problem. When I try to debug the tzpes in CVF the simulation does not stop at the b reakpoints. The simulation just run trough (or gives an error) but does not stop at the setted breakpoints. I suspect the DF60.PDB file to have to do something with the problem because when I debug sometimes CVF asks locate the DF60.PDB file. I indicate the location in the userlibs\debug and then the CVF gives and error and needs to be closed. After this procedure the project does not seem to be debugable anymore. I am a bit confused! Maybe someone can help me?

Tanks in advance

max


¡Y compártelas en Windows Live Fotos! Estas fiestas diviértete tomando fotos.





************************************************************************************
This footnote confirms that this email message has been scanned by
PineApp Mail-SeCure for the presence of malicious code, vandals & computer viruses.
************************************************************************************






************************************************************************************
This footnote confirms that this email message has been scanned by
PineApp Mail-SeCure for the presence of malicious code, vandals & computer viruses.
************************************************************************************