Tools to Help You Understand Traceback Output

When an application fails and you need to diagnose the error, there are a few tools and aids that are helpful. Compiler-generated machine code listings and linker-generated map files can help you understand the affects of compiler optimizations and to see how your application is laid out in memory. They may help you interpret the information provided in a stack trace at the time of the error:

To generate a complete listing (.lst) file:

• When using the Microsoft visual development environment:
  
  1. Choose Settings from the Project menu
  2. Click the Fortran tab
  3. Select the Listing Files category
  4. Click (check) "Source Listing"
  5. Click "Machine Code"
  6. Click "Include Files"
  7. Make any other changes needed to the Project Settings, then click OK.
     
     
• When compiling from the command line, specify /list with /show:all:

    DF file.f90 /list /show:all
  

To generate a link map (.map) file:

• When using the visual development environment:
  
  1. Choose Settings from the Project menu
  2. Click the Link tab
  3. Select the General or Debug category
  4. Select Generate mapfile
  5. Make any other changes needed to the Project Settings, then click OK.
     
     
• When compiling from the command line, specify /map:
  

    DF file.f90 /map
  

To see what sections are defined in an executable image (.exe) file:

• Specify the /traceback compile option. This requests that the compiler generate PC correlation information to be used at run-time in the event of an error.
  
  
• This information is gathered up by the linker in the executable image in a section named ".trace". To see what sections are in an image, use the command:
  

    link -dump -summary your_app_name.exe
  

  To see more detailed information, use the command:

    link -dump -headers your_app_name.exe