public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "phil1691 at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/99711] New: Crash when reading an allocated character array in namelist
Date: Mon, 22 Mar 2021 14:02:36 +0000 [thread overview]
Message-ID: <bug-99711-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99711
Bug ID: 99711
Summary: Crash when reading an allocated character array in
namelist
Product: gcc
Version: 10.2.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: fortran
Assignee: unassigned at gcc dot gnu.org
Reporter: phil1691 at gmail dot com
Target Milestone: ---
The following code crashes with a segmentation fault (gcc 10.2.0):
> cat alloc_nml.f90
program allocnml
implicit none
character(len=:), dimension(:), allocatable :: cbulist_ru
integer :: iluseg
namelist /nam_bu_ru/ cbulist_ru
allocate( character(len=10) :: cbulist_ru(5) )
open(newunit=iluseg, file='list.nml', status='old', &
action='read', form='formatted', access='sequential')
read(unit=iluseg, nml=nam_bu_ru)
print *, cbulist_ru
close(unit=iluseg)
end program allocnml
With the following namelist file:
> cat list.nml
&NAM_BU_RU
CBULIST_RU(1) = 'PRES'
CBULIST_RU(2) = 'NEST'
CBULIST_RU(3) = 'HTURB'
CBULIST_RU(4) = 'VTURB'
/
Compilation:
> gfortran -g alloc_nml.f90
Execution:
> ./a.out
Program received signal SIGSEGV: Segmentation fault - invalid memory reference.
Backtrace for this error:
#0 0x146bdba3349f in ???
#1 0x146bdbb57d7a in ???
#2 0x146bdc79df4b in nml_read_obj
at ../../../gcc-10.2.0-srcdir/libgfortran/io/list_read.c:3142
#3 0x146bdc79ee8a in nml_get_obj_data
at ../../../gcc-10.2.0-srcdir/libgfortran/io/list_read.c:3512
#4 0x146bdc7a78b7 in finalize_transfer
at ../../../gcc-10.2.0-srcdir/libgfortran/io/transfer.c:4128
#5 0x400d48 in allocnml
at
/home/waup/F90/bug_gcc/character_allocatable_namelist/alloc_nml.f90:14
#6 0x400e20 in main
at
/home/waup/F90/bug_gcc/character_allocatable_namelist/alloc_nml.f90:19
Erreur de segmentation (core dumped)
next reply other threads:[~2021-03-22 14:02 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-22 14:02 phil1691 at gmail dot com [this message]
2021-03-23 1:11 ` [Bug fortran/99711] " jvdelisle at gcc dot gnu.org
2021-03-23 2:11 ` kargl at gcc dot gnu.org
2021-03-23 2:29 ` jvdelisle at gcc dot gnu.org
2021-03-23 2:41 ` jvdelisle at gcc dot gnu.org
2021-03-23 6:16 ` sgk at troutmask dot apl.washington.edu
2021-03-23 7:37 ` philippe.wautelet at aero dot obs-mip.fr
2021-03-24 2:41 ` jvdelisle at gcc dot gnu.org
2021-03-24 3:15 ` jvdelisle at gcc dot gnu.org
2021-03-24 5:35 ` sgk at troutmask dot apl.washington.edu
2021-03-24 5:45 ` sgk at troutmask dot apl.washington.edu
2021-03-25 3:32 ` jvdelisle at gcc dot gnu.org
2021-03-26 1:47 ` jvdelisle at gcc dot gnu.org
2021-03-26 2:25 ` jvdelisle at gcc dot gnu.org
2021-03-26 2:38 ` jvdelisle at gcc dot gnu.org
2021-03-26 6:04 ` sgk at troutmask dot apl.washington.edu
2021-03-26 23:38 ` jvdelisle at gcc dot gnu.org
2021-03-27 3:14 ` jvdelisle at gcc dot gnu.org
2023-08-31 12:58 ` philippe.wautelet at aero dot obs-mip.fr
2023-08-31 17:20 ` sgk at troutmask dot apl.washington.edu
2023-08-31 17:22 ` kargl at gcc dot gnu.org
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-99711-4@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@gcc.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).