public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "hjl.tools at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/66927] [6 Regression] ICE in gfc_conf_procedure_call Date: Sun, 25 Oct 2015 16:47:00 -0000 [thread overview] Message-ID: <bug-66927-4-eVp0NRyTzi@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-66927-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66927 --- Comment #11 from H.J. Lu <hjl.tools at gmail dot com> --- On Linux/ia32, I got spawn [open ...]^M *** Error in `./allocate_with_source_10.exe': free(): invalid next size (fast): 0x09dcebc8 *** Program received signal SIGSEGV: Segmentation fault - invalid memory reference. Backtrace for this error: #0 0xf7766bdf in ??? #1 0x456e2e68 in ??? #2 0x456e5a03 in ??? #3 0x456e7c5e in ??? #4 0x45658960 in ??? #5 0x4565ebf2 in ??? #6 0x4565a4e3 in ??? #7 0x4565e481 in ??? #8 0x457a35fb in ??? #9 0x4565a4e3 in ??? #10 0x457a36f0 in ??? #11 0x45777192 in ??? #12 0x45777424 in ??? #13 0x45688969 in ??? #14 0x456dbf12 in ??? #15 0x456e4899 in ??? #16 0x456e7f3f in ??? #17 0x804916e in ??? #18 0x80492a2 in ??? #19 0x80492e2 in ??? #20 0x456896f4 in ??? #21 0x8048780 in ??? FAIL: gfortran.dg/allocate_with_source_10.f08 -O0 execution test GCC is configured with --prefix=/usr/6.0.0 --enable-clocale=gnu --with-system-zlib --enable-shared --with-demangler-in-ld --enable-libmpx i686-linux --with-fpmath=sse --enable-languages=c,c++,fortran,java,lto,objc
next prev parent reply other threads:[~2015-10-25 16:47 UTC|newest] Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-07-18 9:40 [Bug fortran/66927] New: [6.0 regression] " juergen.reuter at desy dot de 2015-07-18 9:41 ` [Bug fortran/66927] " juergen.reuter at desy dot de 2015-07-18 9:55 ` dominiq at lps dot ens.fr 2015-07-18 9:58 ` vehre at gcc dot gnu.org 2015-07-18 10:01 ` juergen.reuter at desy dot de 2015-07-18 13:01 ` vehre at gcc dot gnu.org 2015-07-21 7:58 ` [Bug fortran/66927] [6 Regression] " rguenth at gcc dot gnu.org 2015-08-06 10:09 ` vehre at gcc dot gnu.org 2015-10-06 8:40 ` vehre at gcc dot gnu.org 2015-10-16 8:34 ` rguenth at gcc dot gnu.org 2015-10-25 12:29 ` vehre at gcc dot gnu.org 2015-10-25 13:03 ` vehre at gcc dot gnu.org 2015-10-25 16:47 ` hjl.tools at gmail dot com [this message] 2015-10-25 18:04 ` vehre at gcc dot gnu.org 2015-10-26 13:04 ` vehre at gcc dot gnu.org 2015-10-26 22:43 ` juergen.reuter at desy dot de 2015-10-26 23:42 ` juergen.reuter at desy dot de 2015-10-27 0:55 ` kargl at gcc dot gnu.org 2015-10-27 1:01 ` juergen.reuter at desy dot de
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-66927-4-eVp0NRyTzi@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: linkBe 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).