------- Comment #3 from kargl at gcc dot gnu dot org 2009-01-04 19:46 -------
Using gfortran 4.3.3, a segfault also occurs but the backtrace is different.
(gdb) run
Starting program: /usr/home/kargl/tmp/z
[New LWP 100173]
[New Thread 48301140 (LWP 100173)]
10 10
1 1
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 48301140 (LWP 100173)]
0x481d5aa3 in malloc_usable_size () from /lib/libc.so.7
(gdb) bt
#0 0x481d5aa3 in malloc_usable_size () from /lib/libc.so.7
#1 0x481d63a7 in free () from /lib/libc.so.7
#2 0x080489c0 in MAIN__.omp_fn.0 (.omp_data_i=0x0) at gib.f90:31
#3 0x08048db2 in test_omp () at gib.f90:5
#4 0x08048e61 in main (argc=Error accessing memory address 0x0: Bad address.
)
at ../.././..//gcc-4.3-20081120/libgfortran/fmain.c:21
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=38724
