[Bug fortran/34153] Debugging: Cannot set breakpoint in comment lines or END PROGRAM

2009-05-13 Thread burnus at gcc dot gnu dot org
--- Comment #4 from burnus at gcc dot gnu dot org 2009-05-13 14:53 --- Subject: Bug 34153 Author: burnus Date: Wed May 13 14:52:54 2009 New Revision: 147477 URL: http://gcc.gnu.org/viewcvs?root=gccview=revrev=147477 Log: 2009-05-13 Tobias Burnus bur...@net-b.de PR

[Bug fortran/34153] Debugging: Cannot set breakpoint in comment lines or END PROGRAM

2009-05-13 Thread burnus at gcc dot gnu dot org
--- Comment #5 from burnus at gcc dot gnu dot org 2009-05-13 16:14 --- FIXED on the trunk (4.5). Thanks for the bug report! -- burnus at gcc dot gnu dot org changed: What|Removed |Added

[Bug fortran/34153] Debugging: Cannot set breakpoint in comment lines or END PROGRAM

2009-05-12 Thread burnus at gcc dot gnu dot org
--- Comment #3 from burnus at gcc dot gnu dot org 2009-05-12 21:10 --- I have a patch for this. Note, however, that the compiler - even with default options - (too) aggressively optimizes your program, i.e. the assignment is optimized away even with -O0 and thus for your program the

[Bug fortran/34153] Debugging: Cannot set breakpoint in comment lines or END PROGRAM

2007-11-20 Thread burnus at gcc dot gnu dot org
--- Comment #1 from burnus at gcc dot gnu dot org 2007-11-20 11:34 --- The problem is that you end up in the wrong file. If you enter break 3 you are debugging the wrapping program not the Fortran program test, which is the reason that there is no i available. Try: break file.f:line,

[Bug fortran/34153] Debugging: Cannot set breakpoint in comment lines or END PROGRAM

2007-11-20 Thread fxcoudert at gcc dot gnu dot org
--- Comment #2 from fxcoudert at gcc dot gnu dot org 2007-11-20 13:10 --- (In reply to comment #1) The problem is that you end up in the wrong file. If you enter break 3 you are debugging the wrapping program not the Fortran program test, which is the reason that there is no i