Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

DEBUGING DLL FROM RELEASE EXE

Status
Not open for further replies.

alquimixta

Programmer
Sep 10, 2010
3
ES
Hello.

I'm trying to debug a DLL called from a release executable, in Compaq Visual Fortran. I have created a Dynamic link library project and I have compiled the source files. When I run the mainly program (Build => Start Debug => Go) but the breakpoints are ignored in the dll, so the executab le doesn't stop and I don't get the value variables

My project is set up as follows (most imporant issues):

Project Settings => Debug Tab => Category: General => Executable for debug session, working directory and program arguments OK

Project Settings => Debug Tab => Category: Additional DLLS => Loxal Name OK

Project Settings => Fortran Tab
General Check the box for "Generate Source Browser Information"
Libraries Use Fortran Run-time Libraries should be set to
Debug Single-Threaded
Preprocessor Enter: \trnsys15\include" for Custom INCLUDE and USE paths
Run Time check boxes next to all "Runtime Error Checking" options
Check box next to "Generate Traceback Info"

Project Settings => Link Tab
General Output File Name OK



I have tried several things without results, I'll be glad with some king of help.
 
Make sure the .pdb file is in the same directory as the DLL.
 
The .pdb wasn't in the same file as the DLL. I put it in the same folder and i tried without results.

I have to say too that when I run the Debug (run to cursor or Go) the simbols from the DLL are loaded, and I can see the sources codes but for some reason it seems don't match the sources with the DLL

I did a lots of test and I don't have more ideas...
 
Maybe this can be useful:

The DLL isn't called directly from the executable, the exe set up in the "Debug Tab" call another procces wich call the library.

From my way when I debug I don't see the DLL in the modules, but if i attach to the procces that call the library my DLL appears in the modules, but not the source codes.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top