Le 04/04/2012 12:13, Fabian Wein a écrit :
Hello,
I'm actually a C++ developer but have to work with FORTRAN 77 for
a project.
I have the most current eclipse stuff. gcc is 4.5.1,
The debugger tends to exit with -1. With gdb (GDB) SUSE (7.2-3.3)
from Suse 11.1
I could not proceed from the first breakpoint.
I upgraded gdb to gdb (GDB) SUSE (7.4.50.20120120-79.1) and now it
works better,
but all of a sudden gdb exits before.
Hello,
I have been using photran on opensuse (and Windows) for several
years (currently opensuse 12.1 and gdb 7.3-41.1.2).
The link with gdb has always been the weakest point of photran for
me, since I have never been able to use it really predictably
although I only have crashes when I want to see the content of some
arrays (not the case for others arrays).
In an old thread on this list
http://dev.eclipse.org/mhonarc/lists/photran/msg01509.html), you can
find the following sentence by Greg Watson (Date: Wed, 3
Nov 2010):
"Photran does not provide its own debugger, but rather relies
on the CDT debugger which is designed for sequential C/C++
programs. This is why debugging Fortran programs is often
problematic. Unfortunately this is likely to remain the case until
someone either improves the CDT debugger to work better with
Photran, or creates a Fortran debugger for Photran."
It seems to me, it is still the case...
PS: Another annoying "feature" for debugging purposes is that when
you execute a code, most of the time, printouts do not appear in the
"console" tab when they are executed, but only at the end of the
execution.
PS2: you may find more help in
http://help.eclipse.org/indigo/index.jsp?topic=/org.eclipse.cdt.doc.user/tasks/cdt_o_run.htm
--
Sincerely yours,
Michel DEVEL
|