This is the mail archive of the
fortran@gcc.gnu.org
mailing list for the GNU Fortran project.
gfortran -fstack-check valgrind Segmentation fault
- From: José Rui Faustino Sousa <jrfsousa at teor dot fis dot uc dot pt>
- To: valgrind-users at lists dot sourceforge dot net, fortran at gcc dot gnu dot org
- Date: Thu, 09 Feb 2012 09:27:55 +0000
- Subject: gfortran -fstack-check valgrind Segmentation fault
Hi all!
I am not sure if this should go to valgrind or to gfortran, so it goes
both ways... ;-)
I may be doing something wrong and Google is not very helpful, but it
does look buggy to me:
$ cat ./tst.f90
program empty
implicit none
stop
end program empty
$ gfortran -g -fstack-check -o ./tst ./tst.f90
$ valgrind --tool=memcheck ./tst
==****== Memcheck, a memory error detector
[...]
==****== ERROR SUMMARY: 1 errors from 1 contexts (suppressed: 4 from 4)
Segmentation fault
$ gfortran -g -o ./tst ./tst.f90
$ valgrind --tool=memcheck ./tst
==****== Memcheck, a memory error detector
[...]
==****== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 4 from 4)
$
$ gfortran --version
GNU Fortran (Ubuntu 4.4.3-4ubuntu5) 4.4.3
Copyright (C) 2010 Free Software Foundation, Inc.
GNU Fortran comes with NO WARRANTY, to the extent permitted by law.
You may redistribute copies of GNU Fortran
under the terms of the GNU General Public License.
For more information about these matters, see the file named COPYING
$ valgrind --version
valgrind-3.7.0
$ uname -a
Linux tricana 2.6.32-37-generic #81-Ubuntu SMP Fri Dec 2 20:32:42 UTC
2011 x86_64 GNU/Linux
$
I also tried with the Ubuntu default valgrind package 3.6.0
I would be nice if DWARF support improved so that --read-var-info=yes
would work properly.
Thank you very much for the great packages!
Best regards,
Josà Rui