public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "tkoenig at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libfortran/98129] Failure on reading big chunk of /dev/urandom
Date: Fri, 04 Dec 2020 12:40:34 +0000	[thread overview]
Message-ID: <bug-98129-4-iW7v7pjEzF@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-98129-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98129

--- Comment #2 from Thomas Koenig <tkoenig at gcc dot gnu.org> ---
The problem seems to be related to an early return from the read system call:

strace -e trace=open,read,close ./a.out
read(3, "\177ELF\2\1\1\0\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0\0\v\2\0\0\0\0\0"...,
832) = 832
close(3)                                = 0
close(3)                                = 0
read(3, "\177ELF\2\1\1\3\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0P\217\0\0\0\0\0\0"...,
832) = 832
close(3)                                = 0
read(3, "\177ELF\2\1\1\0\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0\260/\0\0\0\0\0\0"...,
832) = 832
close(3)                                = 0
read(3, "\177ELF\2\1\1\0\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0@*\0\0\0\0\0\0"..., 832)
= 832
close(3)                                = 0
read(3, "\177ELF\2\1\1\3\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0`D\2\0\0\0\0\0"..., 832)
= 832
close(3)                                = 0
read(3,
":\312\275\302\373|\204[c`\20\275\230\205\326@\255Mj\263-qd\336\30\300\2G\326\215\333J"...,
40000000) = 33554431
At line 9 of file read.f90
Fortran runtime error: End of file

Error termination. Backtrace:
close(5)                                = 0
close(5)                                = 0
close(6)                                = 0
close(5)                                = 0
close(5)                                = 0
close(5)                                = 0
close(6)                                = 0
close(5)                                = 0
close(6)                                = 0
close(5)                                = 0
#0  0x7fd9847c572f in read_block_direct
        at ../../../trunk/libgfortran/io/transfer.c:664
#1  0x7fd9847c572f in unformatted_read
        at ../../../trunk/libgfortran/io/transfer.c:1127
#2  0x400bf3 in ???
#3  0x400c9c in ???
#4  0x7fd983a46349 in __libc_start_main
        at ../csu/libc-start.c:308
#5  0x400909 in ???
        at ../sysdeps/x86_64/start.S:120
#6  0xffffffffffffffff in ???
close(4)                                = 0
close(3)                                = 0
+++ exited with 2 +++

  parent reply	other threads:[~2020-12-04 12:40 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-03 20:01 [Bug libfortran/98129] New: " tkoenig at gcc dot gnu.org
2020-12-04 10:41 ` [Bug libfortran/98129] " dominiq at lps dot ens.fr
2020-12-04 12:40 ` tkoenig at gcc dot gnu.org [this message]
2020-12-04 12:50 ` tkoenig at gcc dot gnu.org
2020-12-04 15:27 ` kargl at gcc dot gnu.org
2020-12-04 16:17 ` tkoenig at gcc dot gnu.org
2020-12-04 18:16 ` kargl at gcc dot gnu.org
2020-12-04 18:37 ` anlauf at gcc dot gnu.org
2020-12-04 21:32 ` anlauf at gcc dot gnu.org
2020-12-04 22:09 ` anlauf at gcc dot gnu.org
2020-12-04 22:28 ` tkoenig at gcc dot gnu.org
2020-12-04 22:38 ` anlauf at gcc dot gnu.org
2021-01-21 21:58 ` anlauf at gcc dot gnu.org
2021-01-22 12:12 ` anlauf 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-98129-4-iW7v7pjEzF@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).