- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello, I am having some trouble configuring VS 2010 to debug a fortran dll.
The dll is a project and is in a solution witha cpp project, which is the main program.
The cpp project is configured to be the startup project
Project dependencies have the cpp project depending on the dll project
Fortran dll project Linker, General, Output File is $(SolutionDir)\\Debug\\$(ProjectName).dll
The dll, lib, and pdb files are all located in the solution, debug folder after the build, as expected.
the command line is /nologo /debug:full /Od /warn:interfaces /module:"Debug\\\\" /object:"Debug\\\\" /Fd"Debug\\vc100.pdb" /traceback /check:bounds /libs:dll /threads /dbglibs /c
The breakpoints have the open circle, with the message that no symbols have been loaded for this document.
The dll does not appear in the list of debug modules.
What am i missing?
Thanks
The dll is a project and is in a solution witha cpp project, which is the main program.
The cpp project is configured to be the startup project
Project dependencies have the cpp project depending on the dll project
Fortran dll project Linker, General, Output File is $(SolutionDir)\\Debug\\$(ProjectName).dll
The dll, lib, and pdb files are all located in the solution, debug folder after the build, as expected.
the command line is /nologo /debug:full /Od /warn:interfaces /module:"Debug\\\\" /object:"Debug\\\\" /Fd"Debug\\vc100.pdb" /traceback /check:bounds /libs:dll /threads /dbglibs /c
The breakpoints have the open circle, with the message that no symbols have been loaded for this document.
The dll does not appear in the list of debug modules.
What am i missing?
Thanks
Link Copied
4 Replies
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I usually recommend against directing the output of one project into the output directory of another, as this can cause intermediate information to be removed. Please reset the output directory of the DLL project to be its own output directory and add a post-build step to copy the DLL into the executable output directory.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Thanks for the reply; i like youradvice about managing the files, and made the changes to our main application solution.
Debugging still did not work for the main solution, but I it did workon a small test solution, which was encouraging.
After applying the recentupdate to v12.1, however, debugging worked for the main application on all but one workstation.
Since we are all using Team Foundation Server, the project propertiesare identical on all the workstations, so I suspect a setting in VS; does that sound right?
The workstation that is not debugging has only a few modules loaded in Debug, Window, Modules, so we cant follow the recommendations that begin with "rightclick on the module".
Any ideas?
Debugging still did not work for the main solution, but I it did workon a small test solution, which was encouraging.
After applying the recentupdate to v12.1, however, debugging worked for the main application on all but one workstation.
Since we are all using Team Foundation Server, the project propertiesare identical on all the workstations, so I suspect a setting in VS; does that sound right?
The workstation that is not debugging has only a few modules loaded in Debug, Window, Modules, so we cant follow the recommendations that begin with "rightclick on the module".
Any ideas?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello, still would like some help with debugging.
when I start the debugger, the modules window does not list the fortran project dll file, at all.
the program runs, however, so I know the dll can be found
thanks,
when I start the debugger, the modules window does not list the fortran project dll file, at all.
the program runs, however, so I know the dll can be found
thanks,
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Try setting "Project > Properties > Debugging > Debugger Type" to Mixed or Native. If this property is set to Managed or Auto chooses Managed at runtime, Fortran .dll files will not show up in the modules window.

Reply
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page