debugging a dll

[menchar]

Do I need to link my CVI executable to the debug versions of the export libraries when I want to debug a DLL?

CVI generates debug versions of both the dll and the export library when you build the dll in debug mode.

Does CVI automagically switch when debugging the executable and I want to trace into the DLL?

Menchar

[menchar]

And here's another mystery.

I have a dll with a dll main entry point.

On process attach I was initializing the CVI runtime engine.

This was causing a fault.  Getting strange popups from the CVI RTE.

I eliminated RTE init and now OK.

So what are the rules for using the RTE init call in dllmain?  I think I had it in there to get rte going if dll called from a non-CVI app.

Looks like it's not benign if called from a cvi app.

Menchar

[menchar]

What happens if I link both the debug and release versions of the export library into my executable?

[Guillaume Dargaud]

> What happens if I link both the debug and release versions of the export
> library into
> my executable?

Duplicate symbols ?
--
Guillaume Dargaud
http://www.gdargaud.net/

[menchar]

Surprisingly enough, no 🙂

Menchar

[menchar]

To answer some of my own questions since NI can't / won't:

1.  CVI IDE does not automatically switch to using the debug version of a DLL when you try to trace into a CVI-developed DLL from a CVI application.
2.  You have to link the debug version of the export library to be able to trace into a CVI-developed DLL from a debugged CVI application.
3.  If you link both the debug and release versions of the export library into the debugged CVI application, the release mode version is used.  No duplicate symbol errors occur during the link.

[menchar]

G. Dargaud -

I've used your utility, LargeImage - it does a good job.  Thank you for writing it.

Is it truly freeware?  Can we use it at work to view images?

Menchar

[olhass]

I'm using CVI2009 - are there any changes concerning the mentioned behavior?

Or does anyone know a tip/trick e.g. to use build setting/steps or other tools to automatically include different libraries when switching from release to debug version of a exe/dll? (my idea is: i want to create a release and debug-version of each DLL/EXE i'm using, which may include many other release/debuggable DLLs and i don't want to switch each library type every time i change from release to debug version...)

[Kelsey_Weaver@NI]

Hi olhass,

From what I understand, you're wanting to change the different libraries that are built with the DLL or Executable each time you select to build in release or debug mode. BUT you don't want to have to specify the libraries each time... I guess I'm wondering why you're wanting to do this. The point of building in either debug or release mode is so that you can debug the application before you build the release version. So your build specs would most likely be the same. 

Take a look at these resources and see if they're any help for you:

http://zone.ni.com/reference/en-XX/help/370051M-01/cvi/usermanual/prjbldmenudebdlls/

http://digital.ni.com/public.nsf/allkb/2A11A12C31CABDBF86257B570079D84E?OpenDocument

The second link is a Knowledge Base article related to a switching between the build libraries for 32-bit and 64-bit configurations. So the process might be similar for doing what you're asking about. 

Additionally, you'll typically get a better response from the community when you create new posts on the discussion forums as opposed to commenting on old ones. I'd recommend doing that if my post does not lead you to a solution.

[menchar]

6 years later an NI still doesn't understand the issue 😉