Why Am I Getting Annoying Debug Messages When Compiling My Fortran Program?

  • Thread starter Kabuto
  • Start date
In summary: Nt tim = tim+dt(it-1) apo = ap0 ap0 = 0 do I=1,Np1 ap0(I) = k*(dxe(I)+dxe(I+1))/(2*dt(it-1)*rho*cp) ap0(I) = ap0(I)+hp*Dx(I) ap0(I) = ap0(I)+A*L*W*th/(dt(it-1)*dx(I))! Sp(I) = -hp*dx(i) enddo ap0(1) = ap0(1)+Nu/hL ap0(Np1) = ap0
  • #1
Kabuto
8
0
hi,
I would be grateful for any help.
I don't know why I've got these annoying debug messages every time I had compiled my fortran program though, I have'nt made any changes to the settings.

'UOD.exe' (Win32): Loaded 'F:\Lectures\CFD\Fortran\UOD\Debug\UOD.exe'. Symbols loaded.
'UOD.exe' (Win32): Loaded 'C:\Windows\SysWOW64\ntdll.dll'. Loading disabled by Include/Exclude setting.
'UOD.exe' (Win32): Loaded 'C:\Windows\SysWOW64\kernel32.dll'. Loading disabled by Include/Exclude setting.
'UOD.exe' (Win32): Loaded 'C:\Windows\SysWOW64\KernelBase.dll'. Loading disabled by Include/Exclude setting.
'UOD.exe' (Win32): Loaded 'C:\Windows\SysWOW64\imagehlp.dll'. Loading disabled by Include/Exclude setting.
'UOD.exe' (Win32): Loaded 'C:\Windows\SysWOW64\msvcrt.dll'. Loading disabled by Include/Exclude setting.
'UOD.exe' (Win32): Loaded 'C:\Windows\SysWOW64\advapi32.dll'. Loading disabled by Include/Exclude setting.
'UOD.exe' (Win32): Loaded 'C:\Windows\SysWOW64\sechost.dll'. Loading disabled by Include/Exclude setting.
'UOD.exe' (Win32): Loaded 'C:\Windows\SysWOW64\rpcrt4.dll'. Loading disabled by Include/Exclude setting.
'UOD.exe' (Win32): Loaded 'C:\Windows\SysWOW64\sspicli.dll'. Loading disabled by Include/Exclude setting.
'UOD.exe' (Win32): Loaded 'C:\Windows\SysWOW64\cryptbase.dll'. Loading disabled by Include/Exclude setting.
'UOD.exe' (Win32): Loaded 'C:\Program Files\CheckPoint\ZAForceField\WOW64\Plugins\ISWSHEX.dll'. Loading disabled by Include/Exclude setting.
'UOD.exe' (Win32): Loaded 'C:\Windows\winsxs\x86_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.6195_none_d09154e044272b9a\msvcr80.dll'. Loading disabled by Include/Exclude setting.
'UOD.exe' (Win32): Loaded 'C:\Windows\SysWOW64\user32.dll'. Loading disabled by Include/Exclude setting.
'UOD.exe' (Win32): Loaded 'C:\Windows\SysWOW64\gdi32.dll'. Loading disabled by Include/Exclude setting.
'UOD.exe' (Win32): Loaded 'C:\Windows\SysWOW64\lpk.dll'. Loading disabled by Include/Exclude setting.
'UOD.exe' (Win32): Loaded 'C:\Windows\SysWOW64\usp10.dll'. Loading disabled by Include/Exclude setting.
'UOD.exe' (Win32): Loaded 'C:\Windows\SysWOW64\wintrust.dll'. Loading disabled by Include/Exclude setting.
'UOD.exe' (Win32): Loaded 'C:\Windows\SysWOW64\crypt32.dll'. Loading disabled by Include/Exclude setting.
'UOD.exe' (Win32): Loaded 'C:\Windows\SysWOW64\msasn1.dll'. Loading disabled by Include/Exclude setting.
'UOD.exe' (Win32): Loaded 'C:\Windows\winsxs\x86_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.6195_none_d09154e044272b9a\msvcp80.dll'. Loading disabled by Include/Exclude setting.
'UOD.exe' (Win32): Loaded 'C:\Windows\SysWOW64\ole32.dll'. Loading disabled by Include/Exclude setting.
'UOD.exe' (Win32): Loaded 'C:\Windows\SysWOW64\imm32.dll'. Loading disabled by Include/Exclude setting.
'UOD.exe' (Win32): Loaded 'C:\Windows\SysWOW64\msctf.dll'. Loading disabled by Include/Exclude setting.
'UOD.exe' (Win32): Loaded 'C:\Windows\SysWOW64\nvinit.dll'. Loading disabled by Include/Exclude setting.
'UOD.exe' (Win32): Loaded 'C:\Windows\SysWOW64\ntmarta.dll'. Loading disabled by Include/Exclude setting.
'UOD.exe' (Win32): Loaded 'C:\Windows\SysWOW64\Wldap32.dll'. Loading disabled by Include/Exclude setting.
'UOD.exe' (Win32): Loaded 'C:\Program Files\CheckPoint\ZAForceField\WOW64\AK\icsak.dll'. Loading disabled by Include/Exclude setting.
First-chance exception at 0x75E4C41F in UOD.exe: Microsoft C++ exception: std::exception at memory location 0x0014F428.
First-chance exception at 0x75E4C41F in UOD.exe: Microsoft C++ exception: std::exception at memory location 0x0014F428.
'UOD.exe' (Win32): Loaded 'C:\Windows\SysWOW64\psapi.dll'. Loading disabled by Include/Exclude setting.
First-chance exception at 0x75E4C41F in UOD.exe: Microsoft C++ exception: std::exception at memory location 0x0014F7B8.
First-chance exception at 0x75E4C41F in UOD.exe: Microsoft C++ exception: std::exception at memory location 0x0014F7B8.
The thread 0x6ec has exited with code 0 (0x0).
The program '[7120] UOD.exe' has exited with code 0 (0x0).
 
Technology news on Phys.org
  • #2
I'm guessing that most of the "Loading disabled..." messages are informational. The ones that seem more serious are these:
First-chance exception at 0x75E4C41F in UOD.exe: Microsoft C++ exception: std::exception at memory location 0x0014F428.
First-chance exception at 0x75E4C41F in UOD.exe: Microsoft C++ exception: std::exception at memory location 0x0014F428.
'UOD.exe' (Win32): Loaded 'C:\Windows\SysWOW64\psapi.dll'. Loading disabled by Include/Exclude setting.
First-chance exception at 0x75E4C41F in UOD.exe: Microsoft C++ exception: std::exception at memory location 0x0014F7B8.
First-chance exception at 0x75E4C41F in UOD.exe: Microsoft C++ exception: std::exception at memory location 0x0014F7B8.

These suggest to me that your code is doing something it shouldn't. Please show us your code.
 
  • #3
source codes

thank you very much for the reply Mark44.

the code consists of a main program and one subroutine attached also, the data file.

I appreciate your help.
 

Attachments

  • TDMA.zip
    1.8 KB · Views: 219
  • #4
I have compiled it using VS2012 and intel fortran xe2013 on windows 7 platform if that makes any difference.
 
  • #5
It's much better to just paste code into the page (inside [ code ] and [ /code ] tags). I have done that below.
Here is TDMA.f90.
Code:
subroutine TDMA(N,aE,aW,aP,b,M1,M2,T)
!    integer M1,M2,N
!    parameter (N=10, Np1=N+1)
    integer, intent(in) :: N,M1,M2
!    real, dimension(Np1), intent(in) ::aE,aW,aP,b
!    real, dimension(Np1), intent(out) ::T
!    real, dimension(Np1) ::Q,P
    real, dimension(N), intent(in) :: aE, aW, aP, b
    real, dimension(N), intent(out) :: T
!
!   Local Variables Decleration
!
    real, dimension(N) :: Q, P
    integer:: I, Np1
    real:: den
!    
    !allocate (aE(N), aW(N), aP(N), b(N), T(N), Q(N), P(N))    
!    
!Solution
    P(M1) = aE(M1)/aP(M1)
    Q(M1) = b(M1)/aP(M1)
    do I=M1+1,M2
        den = aP(I)-aW(I)*P(I-1)
        P(I) = aE(I)/den
        Q(I) = (b(I)+Q(I-1)*aW(I))/den
    enddo
    T(M2) = Q(M2)
    do I=M2-1,M1,-1
        T(I) = P(I)*T(I+1)+Q(I)
    enddo
end subroutine TDMA

Here is UnsteadyODmain.f90.
Code:
!  Console1.f90 
!
!  FUNCTIONS:
!  Console1 - Entry point of console application.
!

!****************************************************************************
!
!  PROGRAM: Console1
!
!  PURPOSE:  Entry point for the console application.
!
!****************************************************************************

    program UnsOneDim

    implicit none
  ! Constants
    integer N,Np1
    parameter (N = 4)
    parameter (Np1 = N+1)
    ! Variables
    integer:: I,Nt,it
    real:: k,A,h,L,P,th,W,Nu,hp,hL,f,Tinf
    real:: ts,tf,tim,rho,Cp
    real, dimension(Np1):: x,Dx,dxe,T
    real, dimension(Np1):: aE,aW,aP,Sp
    real, dimension(Np1):: Sc,b,Told,ap0,apo
    character*11:: inputFile
    character*10:: outputFile
    real, allocatable:: dt(:)
    inputFile='datainU.txt'
!
! File Operations
!
    open(unit=8,file=inputFile,mode='read')
    !k = 100
    !h = 10
    !W = 0.1
    !th = 0.001
    !L = 0.2
    !f = 1               !implicit scheme
    read(8,*) outputFile
    read(8,*) k,h,Tinf,L,W,th
    read(8,*) rho,cp
    read(8,*) f,ts,tf,Nt
    allocate (dt(Nt))
    read(8,*)((dt(it)),it=1,Nt)
    read(8,*) Told
    close(8)
! Initialization
    Dx = 1.0/N   !  non dimensionalized
    dxe = Dx
    Dx(1) = Dx(2)/2
    Dx(Np1) = Dx(2)/2  ! equal sized volumes
    dxe(Np1)=0          ! no nodes exist beyond the last one
    A = W*th
    P = 2*(W+th)
    Nu = h*L/k
    hp = h*P*L**2
    hL = h*L*A
    Sp = -hp*Dx
    Sc = 0
    tim = 0
    ap0 = rho*cp*L**2*A*Dx
! Half sized boundary volumes
!    Sp(1) = Sp(1)/2.0
!    Sp(Np1) = Sp(Np1)/2.0
! Boundary Conditions
    T(1) = 1     ! specified bc at x=0 and normalized
    open(unit=7,file=outputFile,mode='write')
    write(7,'(''Initial Values at Time = 0'')')
    write(7,'(f10.4)') Told
    
! Coefficients
    aE = 0
    aW = 0
    aE(1:N) = k*A/dxe(1:N)
    aW(2:Np1) = aE(1:N)
    do it=1,Nt
        tim = tim + dt(it)
        apo = ap0/dt(it)
        b = Sc+apo*Told
        aP = aE+aW-Sp+apo
! Bondary Conditions Application
        b(2) = b(2)+aW(2)*T(1)
        aP(Np1) = aP(Np1)+hL
        call TDMA(Np1,aE,aW,aP,b,2,Np1,T)
    ! Body of Console1
!    print *, 'Hello World'
!read *,I
        write(7,'(''Coefficients at Time = '',f10.4)') tim
        write(7,'(''Dt = '', f10.4,//)') dt(it)
write(7,'(4x,''aE'',10x,''aW'',10x,''aP'',10x,''Sp'',10x,\)')
write(7,'(''Sc'',10x,''b'')')
                
        do I=1,Np1
            write(7,10) aE(I),aW(I),aP(I),Sp(I),Sc(I),b(I)
        enddo
        write(7,*)
        write(7,'(f10.4)') T
        Told = T
    enddo

10  format(6(f10.4,2x))    
    
    close(7)
    deallocate(dt)
    end program UnsOneDim

Here is the data:
data2.dat
100 10 20 0.2 0.1 0.001
500 300
1 0 50 3
20 30 50
0 0 0 0 0
 
  • #6
I see problems right at the beginning. In the first line of executable code in your main program, you are attempting to open a file whose name is an uninitialized variable, inputFile. That's a problem.
 
  • #7
but why?
I have put this statement above the open statement

inputFile='datainU.txt'

why this would'nt work?
 
  • #8
or should I put the file name directly into the open statement?
 
  • #9
Kabuto said:
but why?
I have put this statement above the open statement

inputFile='datainU.txt'

why this would'nt work?
I missed that statement.
Kabuto said:
or should I put the file name directly into the open statement?
No, what you did should work.

Maybe your input file is not in the right place. It needs to be in the same directory as the exe file, probably a directory named Debug. If it's not there, you need to provide the full path to that file.
 
  • #10
thanks a lot Mark44 for your kindly help.
 
  • #11
If you look at the documentation for VS2012 and for Intel FORTRAN xe 2013 is there perhaps a list of "command line options" that you may not be aware of that can turn on or off all sorts of diagnostic testing and messages?

Sometimes there is something of the nature "-Quiet" that just turns off all the warnings, urgent, critical, important and just annoying, but you need to find out if there is such an option and how you tell it to provide only mostly what you want. (I did a couple of quick Google searches and didn't find any list or anything else)
 
  • #12
I appreciate your advice Bill, thank you.
but these messages suddenly showed up without any intervention of me.
the problem is I have'nt changed any settings, and my programs kept working well before that
I am frustrated.
I have tried the advice of Mark44 but it still appears.
I don't know what to do?
 
  • #13
This page

http://social.msdn.microsoft.com/Forums/en-US/vsdebug/thread/d0f173d9-dec1-4404-b8d1-09448eccdab7/

describes how someone, perhaps you?, had VS 2102 working just fine and now gets a stream of warning messages that are some of the exact same warnings and diagnostic information you are getting.

Part way down that page someone with what sounds like some experience offers a mouse click that may switch off some of the diagnostic output that you are seeing.

Perhaps you could try some of the things recommended on that page and see if it solves your problem.

He also has some other problems that are not related to what you are describing and can perhaps be ignored.
 
  • #14
thank you Bill for your kindly help
I am grateful.
 

FAQ: Why Am I Getting Annoying Debug Messages When Compiling My Fortran Program?

Why am I receiving so many debug messages?

Debug messages are typically used by developers to help identify and fix issues with a program. These messages are often set to appear frequently during the testing and development phase, but should be minimized or removed entirely in the final version of the program. If you are receiving an excessive amount of debug messages, it could indicate that the program is still in the testing phase or that there are unresolved issues that need to be addressed.

Can I turn off or disable debug messages?

In most cases, yes, you can turn off or disable debug messages. Depending on the program, there may be a specific setting or option to do so. It is important to note that disabling debug messages may make it more difficult to identify and fix issues with the program, so it should only be done if necessary.

Are debug messages harmful to my device?

No, debug messages are not harmful to your device. They are simply text-based messages that are used for troubleshooting purposes. However, if you are receiving a large number of debug messages, it could potentially slow down the performance of the program.

How do I know if a debug message is a real issue or just a warning?

Typically, debug messages are categorized as either informational, warning, or error. Informational messages are just for your information and do not indicate any issues with the program. Warning messages indicate a potential issue that may need to be addressed. Error messages indicate a problem that needs to be fixed in order for the program to function properly. If you are unsure about a specific debug message, you can consult the program's documentation or contact the developer for clarification.

Can I customize the format or appearance of debug messages?

In some cases, yes, you can customize the format or appearance of debug messages. This may depend on the program or the specific tool being used for debugging. However, it is important to note that changing the format or appearance of debug messages may make it more difficult to read and interpret the messages, so it should only be done if absolutely necessary.

Back
Top