If I let gdb "run" the program under Cygwin 64 it fails.
NOTE: in Cygwin 32 gdb and this fortran work together fine.
When I run my fortran program directly it works.
Cycle_length is defined as a 'real'.
write(*,"('(Note: a negative test time will stop run): ',$)")
read (*,*) cycle_length
When I run line by line using gdb I get this:
(Note: a negative test time will stop run): 39 read (*,*)
cycle_length
(gdb)
[1]+ Stopped gdb olx.exe
harryr@HARRYR-PC ~
$ fg
gdb olx.exe
Program received signal SIGTTIN, Stopped (tty input).
_gfortrani_fbuf_read (u=0x22964c, len=0x0)
at /usr/src/debug/gcc-4.8.2-2/libgfortran/io/fbuf.c:235
235 if (readlen < 0)
Under gdb the program acts like it moves on without keyboard input and thus
The cycle_length is never input, has zero length.
Is the Fortran syntax to antiquated for gdb to handle?
Is gdb (in 64-bit) missing something to force it to pause for keyboard input?
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
