https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90813
--- Comment #5 from paul.richard.thomas at gmail dot com <paul.richard.thomas at gmail dot com> --- Hi there, That might well have pinpointed the problem sufficiently. Thanks Paul On Mon, 10 Jun 2019 at 20:18, seurer at gcc dot gnu.org <gcc-bugzi...@gcc.gnu.org> wrote: > > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90813 > > --- Comment #4 from seurer at gcc dot gnu.org --- > So, adding in a -g3 I see: > > Program received signal SIGSEGV: Segmentation fault - invalid memory > reference. > > Backtrace for this error: > #0 0x3fffb7f80477 in ??? > #1 0x10000878 in MAIN__ > at > /home/seurer/gcc/gcc-test2/gcc/testsuite/gfortran.dg/proc_ptr_51.f90:35 > #2 0x10000878 in main > at > /home/seurer/gcc/gcc-test2/gcc/testsuite/gfortran.dg/proc_ptr_51.f90:32 > Segmentation fault > > > line 35 of the test case is: > res => c_() > > which looks like some kind of call via a function pointer maybe? > > Is there some specific trace or dump that would help you that I could > generate? > Be specific about options if so please. Assembler listing maybe? > > -- > You are receiving this mail because: > You are on the CC list for the bug.
