subject:"\[Bug fortran\/83230\] \[8 regression\] segmentation fault in bind C C\/C\+\+"

[Bug fortran/83230] [8 regression] segmentation fault in bind C C/C++

2017-12-04 Thread redi at gcc dot gnu.org

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83230 --- Comment #11 from Jonathan Wakely --- All the more reason to enable compiler warnings.

[Bug fortran/83230] [8 regression] segmentation fault in bind C C/C++

2017-12-04 Thread juergen.reuter at desy dot de

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83230 --- Comment #10 from Jürgen Reuter --- Sorry for my first false positive, but I'm actually lacking experience with C++.

[Bug fortran/83230] [8 regression] segmentation fault in bind C C/C++

2017-12-04 Thread redi at gcc dot gnu.org

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83230 --- Comment #9 from Jonathan Wakely --- As it says at https://gcc.gnu.org/bugs/ ... "Before reporting that GCC compiles your code incorrectly, compile it with gcc -Wall -Wextra and see whether this shows anything wrong with your code."

[Bug fortran/83230] [8 regression] segmentation fault in bind C C/C++

2017-12-04 Thread jakub at gcc dot gnu.org

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83230 --- Comment #8 from Jakub Jelinek --- *** Bug 83263 has been marked as a duplicate of this bug. ***

[Bug fortran/83230] [8 regression] segmentation fault in bind C C/C++

2017-12-04 Thread jakub at gcc dot gnu.org

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83230 Jakub Jelinek changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|---

[Bug fortran/83230] [8 regression] segmentation fault in bind C C/C++

2017-12-03 Thread juergen.reuter at desy dot de

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83230 --- Comment #6 from Jürgen Reuter --- So shall I commit this as an independent C/C++ bug?

[Bug fortran/83230] [8 regression] segmentation fault in bind C C/C++

2017-12-01 Thread juergen.reuter at desy dot de

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83230 --- Comment #5 from Jürgen Reuter --- (In reply to Jakub Jelinek from comment #4) > The Makefile doesn't have any -O* options, is this all without optimizations? > I admit I've been only compiling the fortran source with trunk f951, the > rest wi

[Bug fortran/83230] [8 regression] segmentation fault in bind C C/C++

2017-12-01 Thread jakub at gcc dot gnu.org

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83230 --- Comment #4 from Jakub Jelinek --- The Makefile doesn't have any -O* options, is this all without optimizations? I admit I've been only compiling the fortran source with trunk f951, the rest with the system gcc (6.3.1), but for f951 I've tried

[Bug fortran/83230] [8 regression] segmentation fault in bind C C/C++

2017-12-01 Thread juergen.reuter at desy dot de

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83230 --- Comment #3 from Jürgen Reuter --- This is the full back trace that I get: Program received signal SIGSEGV, Segmentation fault. __GI___libc_free (mem=0x6530302e30202c30) at malloc.c:2931 2931malloc.c: No such file or directory. (gdb) bt #0

[Bug fortran/83230] [8 regression] segmentation fault in bind C C/C++

2017-12-01 Thread juergen.reuter at desy dot de

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83230 --- Comment #2 from Jürgen Reuter --- I see this problem both on MAC OS X 10.13.1 with r254916 (and the patch mentioned) as well as on Ubuntu 14.04.5 LTS with r255190. r253161 still worked fine. We see this kind of behaviour in two different bind