This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug fortran/60334] Segmentation fault on character pointer assignments
- From: "janus at gcc dot gnu.org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Thu, 27 Feb 2014 09:54:53 +0000
- Subject: [Bug fortran/60334] Segmentation fault on character pointer assignments
- Auto-submitted: auto-generated
- References: <bug-60334-4 at http dot gcc dot gnu dot org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60334
janus at gcc dot gnu.org changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |janus at gcc dot gnu.org
--- Comment #1 from janus at gcc dot gnu.org ---
(In reply to Antony Lewis from comment #0)
> but compiled with gfortran -Og when run gives
>
> Program received signal 11 (SIGSEGV): Segmentation fault.
I can confirm the segfault with 4.8, but I don't see it with trunk. However,
also with trunk one gets some valgrind errors:
==13526== Conditional jump or move depends on uninitialised value(s)
==13526== at 0x4F0E687: _gfortran_transfer_character (in
/usr/lib/x86_64-linux-gnu/libgfortran.so.3.0.0)
==13526== by 0x400806: MAIN__ (c0.f90:8)
==13526== by 0x400835: main (c0.f90:8)
I don't directly see why the code would be invalid.