This is the mail archive of the cygwin@sourceware.cygnus.com mailing list for the Cygwin project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]

Re: Problems with gdb and FORTRAN programs




> I'm writing/debugging some FORTRAN code using egcs 1.1.2 and gdb 4.17.1.
> There seem to be some problems viewing variables with gdb in fortran mode.
> For example,
> 
> Breakpoint 1, getdat_ (data=0xf0be20, m=0x30720d0, n=0x30720d4) at
> snpdata.f:40
> (gdb) print n
> $2 = (PTR TO -> ( integer )) 0x30720d4
> (gdb) set lang c
> Warning: the current language does not match this frame.
> (gdb) print n[0]
> $3 = 491
> (gdb) set lang fortran
> (gdb) print n(1)
> 
> Program received signal SIGSEGV, Segmentation fault.
> 0x30720d9 in ?? ()

Are you compiling your code with -g option i.e. g77 -g xx.f ?
Do not use any optimization flags when compiling a debug versions.

I think you are missing the debug symbols in your binary.


--Suhaib


> The program being debugged stopped while in a function called from GDB.
> When the function (at 0x30720d4) is done executing, GDB will silently
> stop (instead of continuing to evaluate the expression containing
> the function call).
> (gdb)
> 
> How can I view the contents of the variable n in fortran mode?
> 
> Richard Stanton
> 
> 
> --
> Want to unsubscribe from this list?
> Send a message to cygwin-unsubscribe@sourceware.cygnus.com
> 
> 


--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]