Re : Debug problems between Teststand 3.5 and Labwindows CVI 8.0

[Djelloul]

I'm experiencing a problem that is making me crazy...

I have a Dll build under Labwindows CVI 8.0 that is working fine.

To simplify explaination, we will call this Dll "Dll_3".

To use this one, I call another Dll called by Teststand 3.5, that we'll call "Dll_1", that even call another Dll, "Dll_2", to finally point to "Dll_3" (I hope you'll understand )

I've needed some new functions to add in "Dll_3", so I've repected all the stuff to add these functions. 

I compiled and build "Dll_3" without any problem.

I do the same thing with "Dll_2" and "Dll_1" to update them, because the *.lib of "Dll_3" has changed.

Now, here is my problem.

I've added breakpoints on the functions I wanna use and others that already exist in the first version of "Dll_3".

When I use the Debug function of Labwindows CVI (configured to lauch Teststand as external process), and finally point to "Dll_1" (that wil point to "Dll_2" and "Dll_3"), entry in this Dll goes OK.

Same thing for "Dll_2", but when I wanna enter in the new functions of "Dll_3", it's impossible...

The debugger NEVER enter in the new functions. It stops in the already existing functions, but never on the new ones!

The best of the best is that when I check the result of the output parameters, all is OK, its exactly what I'm waiting for!!

So I'm sure that my functions were implemented and taked in charge, but impossible to debug...

I want this to work in Debug mode, because sometimes in Release mode, I have bad results and I wanna know why...

I hope that all these explainations wasn't too boring for you, so if anyone have a clue about why I'm experiencing this, it will be helpful.

By the way, I wanna know why, when I add watching variable in Teststand in debug mode, the running become really slow? (excuse me, really really slow...).

Thanks for the time you spend for reading, and I hope I will found some help on this forum.

Regards, Djelloul

[RayFarmer]

Hi,

You have actually built DLL_3 in debug mode?

Regards

Ray Farmer

[Djelloul]

Yes of course.

I've checked this point 3 times...

But you're right to mention it, because sometimes simple things are hard to find when you concentrate on another difficult point.

I've tried to go through "Dll_3" in debug mode one more time since your message, and the same thing happens

Impossible to debug the new functions added...

[RayFarmer]

Hi,

You have linked the other DLL's to the updated LIB file or moved the updated cdb file to you target system? The cdb file conatins the debug information.

Regards

Ray

[Djelloul]

Yes, I've already set the same path for the debug and the release Dll target in the "Target Settings" of CVI/LabWindows.

I have cleared all the *.lib inside my project, and added the new ones generated after a build, to be sure to use the correct ones.

Thanks for your help.

Regards, Djelloul.

[Djelloul]

Now that I'm reading my last message, it seems that you could think that my probleme is finished, but not at all.

I just wanna describe what I've done before, to be sure that I'm correctly using the CVI tools.

Maybe my words "Yes" and "Thanks for your help" are too much in my message...

Excuse my English, but I'm trying to be as clear and kind as I can.

I hope that someone could help me to understand why my Dll compiled and built with new functions cannot be debuged ONLY when I want to enter on these new ones!

All help will be welcome.

[RayFarmer]

Hi,

Does a function in DLL_3 call a function in DLL_2 call a new function in DLL_1?

I have taken the computer example in TestStand which calls functions contained in a dll call computer.dll. I have created a new dll which exports one function and I have made one of the test call this function.

Now everything works as expected. When I launch TestStand via CVI as Dedub SeqEditor.exe and set some breakpoints, I can step into my new function. Do you use the F8 key to step in to the new function?

The only difference, I'm using CVI 8.5 beta and maybe I only go down one level (depending on your answer above).

Is it possible to supply an simple example showing your problem.

Regards

Ray