Problems with gdb and FORTRAN programs
Tue May 25 15:04:00 GMT 1999
Thanks for the reply, Suhaib.
I did compile using "g77 -f", and the debugging symbols were in the
executable - note that gdb in fortran mode could tell me that "n" was a
pointer to an integer, and in c mode I could even print the contents of n.
It was just when I tried to access the contents of n in fortran mode that
gdb crashed on me.
> -----Original Message-----
> From: Suhaib M. Siddiqi [ mailto:email@example.com ]
> Sent: Tuesday, May 25, 1999 1:25 PM
> To: Richard Stanton; Cygwin Mailing List
> Subject: 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
> > $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.
> > 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 firstname.lastname@example.org
Want to unsubscribe from this list?
Send a message to email@example.com
More information about the Cygwin