[Bug fortran/23375] show location for runtime errors

2006-09-28 Thread fxcoudert at gcc dot gnu dot org
--- Comment #10 from fxcoudert at gcc dot gnu dot org 2006-09-28 07:59 --- Closing, as the error messages have been modified to include source location. -- fxcoudert at gcc dot gnu dot org changed: What|Removed |Added -

[Bug fortran/23375] show location for runtime errors

2006-09-20 Thread tobias dot burnus at physik dot fu-berlin dot de
--- Comment #9 from tobias dot burnus at physik dot fu-berlin dot de 2006-09-20 11:57 --- I think this is fixed. If there are other errors, not covered, one could still reopen this bug or create a new one. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=23375

[Bug fortran/23375] show location for runtime errors

2006-06-07 Thread fxcoudert at gcc dot gnu dot org
--- Comment #8 from fxcoudert at gcc dot gnu dot org 2006-06-07 09:12 --- I wasn't aware of the existence of this PR. I think the problem is a least partly fixed by my recent patch. Are there other runtime errors where we don't issue a source location? -- fxcoudert at gcc dot gnu do

[Bug fortran/23375] show location for runtime errors

2006-06-01 Thread pinskia at gcc dot gnu dot org
--- Comment #7 from pinskia at gcc dot gnu dot org 2006-06-01 21:50 --- *** Bug 27868 has been marked as a duplicate of this bug. *** -- pinskia at gcc dot gnu dot org changed: What|Removed |Added ---

[Bug fortran/23375] show location for runtime errors

2006-05-24 Thread tkoenig at gcc dot gnu dot org
--- Comment #6 from tkoenig at gcc dot gnu dot org 2006-05-24 20:48 --- (In reply to comment #5) > So, how to make a patch for this: > Create a runtime_error_with_loc in gcc-4.1.0/libgfortran/runtime/error.c that > uses the a line number and filename. > > Change the gfor_fndecl_runtime

[Bug fortran/23375] show location for runtime errors

2006-05-24 Thread jjcogliati-r1 at yahoo dot com
--- Comment #5 from jjcogliati-r1 at yahoo dot com 2006-05-24 12:49 --- (In reply to comment #4) > (In reply to comment #3) > > > So in GCC 4.1.0, the only problem seems to be that _gfortran_runtime_error > > is > > not printing the filename and the line number and the line number seem

[Bug fortran/23375] show location for runtime errors

2006-05-23 Thread tkoenig at gcc dot gnu dot org
--- Comment #4 from tkoenig at gcc dot gnu dot org 2006-05-23 21:41 --- (In reply to comment #3) > So in GCC 4.1.0, the only problem seems to be that _gfortran_runtime_error is > not printing the filename and the line number and the line number seems to be > the line number of the previ

[Bug fortran/23375] show location for runtime errors

2006-05-10 Thread jjcogliati-r1 at yahoo dot com
--- Comment #3 from jjcogliati-r1 at yahoo dot com 2006-05-10 13:54 --- (In reply to comment #1) > Confirmed. Though sometimes I wonder if this is an over use of printf style > debugging. > Well, I have a fortran program. It ran fine for the first 10 and a half hours. Then it died

[Bug fortran/23375] show location for runtime errors

2006-03-21 Thread pinskia at gcc dot gnu dot org
--- Comment #2 from pinskia at gcc dot gnu dot org 2006-03-21 23:36 --- *** Bug 26791 has been marked as a duplicate of this bug. *** -- pinskia at gcc dot gnu dot org changed: What|Removed |Added ---

[Bug fortran/23375] show location for runtime errors

2005-08-13 Thread pinskia at gcc dot gnu dot org
--- Additional Comments From pinskia at gcc dot gnu dot org 2005-08-13 17:50 --- Confirmed. Though sometimes I wonder if this is an over use of printf style debugging. -- What|Removed |Added --