public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug fortran/29677]  New: minimally informative  gfortran -fbounds-check
@ 2006-10-31 21:25 mkeehan at lic dot co dot nz
  2006-10-31 21:38 ` [Bug fortran/29677] " kargl at gcc dot gnu dot org
                   ` (4 more replies)
  0 siblings, 5 replies; 6+ messages in thread
From: mkeehan at lic dot co dot nz @ 2006-10-31 21:25 UTC (permalink / raw)
  To: gcc-bugs

My boss teared my hair off with heavy sarcasm when we turned on -fbound-check.

The runtime executable proudly reported an array reference out of bounds.

My boss screamed "Which bloody one?!"

While I am very happy to know we have an array reference out of bounds
I can see his point. Could the error message say which array is out of bounds? 

gfortran 4.1.1


-- 
           Summary: minimally informative  gfortran -fbounds-check
           Product: gcc
           Version: 4.1.1
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: fortran
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: mkeehan at lic dot co dot nz
  GCC host triplet: SLES 9 opteron
GCC target triplet: x86_64-unknown-linux-gnu


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=29677


^ permalink raw reply	[flat|nested] 6+ messages in thread

* [Bug fortran/29677] minimally informative  gfortran -fbounds-check
  2006-10-31 21:25 [Bug fortran/29677] New: minimally informative gfortran -fbounds-check mkeehan at lic dot co dot nz
@ 2006-10-31 21:38 ` kargl at gcc dot gnu dot org
  2006-10-31 21:41 ` pinskia at gcc dot gnu dot org
                   ` (3 subsequent siblings)
  4 siblings, 0 replies; 6+ messages in thread
From: kargl at gcc dot gnu dot org @ 2006-10-31 21:38 UTC (permalink / raw)
  To: gcc-bugs



------- Comment #1 from kargl at gcc dot gnu dot org  2006-10-31 21:38 -------
Upgrade to the a 4.2 pre-release version of gfortran or
the mainline version.  Please report back if you find
a problem.


-- 

kargl at gcc dot gnu dot org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |WAITING


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=29677


^ permalink raw reply	[flat|nested] 6+ messages in thread

* [Bug fortran/29677] minimally informative  gfortran -fbounds-check
  2006-10-31 21:25 [Bug fortran/29677] New: minimally informative gfortran -fbounds-check mkeehan at lic dot co dot nz
  2006-10-31 21:38 ` [Bug fortran/29677] " kargl at gcc dot gnu dot org
@ 2006-10-31 21:41 ` pinskia at gcc dot gnu dot org
  2006-10-31 21:48 ` pinskia at gcc dot gnu dot org
                   ` (2 subsequent siblings)
  4 siblings, 0 replies; 6+ messages in thread
From: pinskia at gcc dot gnu dot org @ 2006-10-31 21:41 UTC (permalink / raw)
  To: gcc-bugs



------- Comment #2 from pinskia at gcc dot gnu dot org  2006-10-31 21:41 -------
The other thing is with debugging option such as -fbounds-check, you can also
use gdb to figure out which one.


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=29677


^ permalink raw reply	[flat|nested] 6+ messages in thread

* [Bug fortran/29677] minimally informative  gfortran -fbounds-check
  2006-10-31 21:25 [Bug fortran/29677] New: minimally informative gfortran -fbounds-check mkeehan at lic dot co dot nz
  2006-10-31 21:38 ` [Bug fortran/29677] " kargl at gcc dot gnu dot org
  2006-10-31 21:41 ` pinskia at gcc dot gnu dot org
@ 2006-10-31 21:48 ` pinskia at gcc dot gnu dot org
  2006-11-01 14:01 ` tobias dot burnus at physik dot fu-berlin dot de
  2006-11-16  7:51 ` fxcoudert at gcc dot gnu dot org
  4 siblings, 0 replies; 6+ messages in thread
From: pinskia at gcc dot gnu dot org @ 2006-10-31 21:48 UTC (permalink / raw)
  To: gcc-bugs



------- Comment #3 from pinskia at gcc dot gnu dot org  2006-10-31 21:48 -------
*** Bug 29678 has been marked as a duplicate of this bug. ***


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=29677


^ permalink raw reply	[flat|nested] 6+ messages in thread

* [Bug fortran/29677] minimally informative  gfortran -fbounds-check
  2006-10-31 21:25 [Bug fortran/29677] New: minimally informative gfortran -fbounds-check mkeehan at lic dot co dot nz
                   ` (2 preceding siblings ...)
  2006-10-31 21:48 ` pinskia at gcc dot gnu dot org
@ 2006-11-01 14:01 ` tobias dot burnus at physik dot fu-berlin dot de
  2006-11-16  7:51 ` fxcoudert at gcc dot gnu dot org
  4 siblings, 0 replies; 6+ messages in thread
From: tobias dot burnus at physik dot fu-berlin dot de @ 2006-11-01 14:01 UTC (permalink / raw)
  To: gcc-bugs



------- Comment #4 from tobias dot burnus at physik dot fu-berlin dot de  2006-11-01 14:01 -------
This has been fixed in the meanwhile.
(Don't forget, gfortran is not that old.)

Possibilities:
- Use a GCC 4.1 branch build (newer than 4.1.1)
- Use a GCC 4.2 branch build
- Use a GCC 4.3 trunk build

For openSUSE 10.x and SLED/SLES exist such packages (made by SUSE), for
SL/SLES/SLED 9.x unfortunally not.

I would suggest to download a gfortran 4.2 or gfortran 4.3 build, both
available e.g. at http://www.physik.fu-berlin.de/~tburnus/gcc-trunk/
You probably need also lib64-gmp4.2.1-mpfr2.2.0.tar.gz

 * * *

Alternatively, run the program in gdb:
gdb ./yourExecutable
(gdb) b _exit
Function "_exit" not defined.
Make breakpoint pending on future shared library load? (y or [n]) y
Breakpoint 1 (_exit) pending.
(gdb) run
[...]
(gdb) bt


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=29677


^ permalink raw reply	[flat|nested] 6+ messages in thread

* [Bug fortran/29677] minimally informative  gfortran -fbounds-check
  2006-10-31 21:25 [Bug fortran/29677] New: minimally informative gfortran -fbounds-check mkeehan at lic dot co dot nz
                   ` (3 preceding siblings ...)
  2006-11-01 14:01 ` tobias dot burnus at physik dot fu-berlin dot de
@ 2006-11-16  7:51 ` fxcoudert at gcc dot gnu dot org
  4 siblings, 0 replies; 6+ messages in thread
From: fxcoudert at gcc dot gnu dot org @ 2006-11-16  7:51 UTC (permalink / raw)
  To: gcc-bugs



------- Comment #5 from fxcoudert at gcc dot gnu dot org  2006-11-16 07:51 -------
Closing, since this was already fixed. Please reopen (or open a new report) if
you have another example of such behaviour with an up-to-date compiler.


-- 

fxcoudert at gcc dot gnu dot org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|WAITING                     |RESOLVED
         Resolution|                            |FIXED


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=29677


^ permalink raw reply	[flat|nested] 6+ messages in thread

end of thread, other threads:[~2006-11-16  7:51 UTC | newest]

Thread overview: 6+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2006-10-31 21:25 [Bug fortran/29677] New: minimally informative gfortran -fbounds-check mkeehan at lic dot co dot nz
2006-10-31 21:38 ` [Bug fortran/29677] " kargl at gcc dot gnu dot org
2006-10-31 21:41 ` pinskia at gcc dot gnu dot org
2006-10-31 21:48 ` pinskia at gcc dot gnu dot org
2006-11-01 14:01 ` tobias dot burnus at physik dot fu-berlin dot de
2006-11-16  7:51 ` fxcoudert at gcc dot gnu dot org

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).