This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug fortran/31251] Non-integer character length leads to segfault
- From: "fxcoudert at gcc dot gnu dot org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 3 May 2007 14:49:17 -0000
- Subject: [Bug fortran/31251] Non-integer character length leads to segfault
- References: <bug-31251-10259@http.gcc.gnu.org/bugzilla/>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
------- Comment #6 from fxcoudert at gcc dot gnu dot org 2007-05-03 15:49 -------
(In reply to comment #5)
> I am not able to reproduce a segfault. However, this patch eliminates the
> double error message. Could someone verify that they still get a segfault
> without this patch and then try with the patch to see what happens.
It's weird. I have applied your patch and rebuilt but I still get the double
error, and the segfault:
pr31251.f90:1.16:
character(len=2.3) :: s
1
Error: Expression at (1) must be of INTEGER type
pr31251.f90:1.16:
character(len=2.3) :: s
1
Error: Expression at (1) must be of INTEGER type
==3668==
==3668== Invalid read of size 4
==3668== at 0x86ED6F1: __gmpn_copyi (in
/home/fxcoudert/svn/debug2/irun/libexec/gcc/i686-pc-linux-gnu/4.3.0/f951)
==3668== Address 0x2 is not stack'd, malloc'd or (recently) free'd
pr31251.f90:0: internal compiler error: Segmentation fault
I don't know what the heck is happening here, but I'll try to understand it
better in the next few days.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=31251