This is the mail archive of the
fortran@gcc.gnu.org
mailing list for the GNU Fortran project.
Re: [Patch, Fortran] PR34186 -fdump-parse-tree fixes
> Or if possible in valgrind?
AFAIK no valgrind for Darwin.
> Can you run it in the debugger and post (in the PR) a backtrace?
Starting program: /opt/gcc/gcc4.3w/libexec/gcc/i686-apple-darwin9/4.3.0/f951 -fdump-parse-tree pr34186.f90
Reading symbols for shared libraries . done
Namespace: A-H: (REAL 4) I-N: (INTEGER 4) O-Z: (REAL 4)
procedure name = func0
symtree: __iso_c_binding Ambig 0
symbol __iso_c_binding (UNKNOWN 0)(MODULE UNKNOWN-INTENT UNKNOWN-ACCESS UNKNOWN-PROC UNKNOWN INTRINSIC)
symtree: c_alert Ambig 0
Program received signal EXC_BAD_ACCESS, Could not access memory.
Reason: KERN_PROTECTION_FAILURE at address: 0x00000000
0x0001cd73 in gfc_show_typespec (ts=0x40e0bb60) at ../../gcc-4.3-work/gcc/fortran/dump-parse-tree.c:82
82 gfc_show_expr (ts->cl->length);
(gdb) backtrace
#0 0x0001cd73 in gfc_show_typespec (ts=0x40e0bb60) at ../../gcc-4.3-work/gcc/fortran/dump-parse-tree.c:82
#1 0x0000000a in ?? ()
Previous frame inner to this frame (gdb could not unwind past this frame)
Dominique