public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "kargl at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libgomp/38724] Segfault with allocatable component in private clause Date: Sun, 04 Jan 2009 19:46:00 -0000 [thread overview] Message-ID: <20090104194602.12116.qmail@sourceware.org> (raw) In-Reply-To: <bug-38724-10110@http.gcc.gnu.org/bugzilla/> ------- 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
next prev parent reply other threads:[~2009-01-04 19:46 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2009-01-04 19:41 [Bug libgomp/38724] New: " kargl at gcc dot gnu dot org 2009-01-04 19:42 ` [Bug libgomp/38724] " kargl at gcc dot gnu dot org 2009-01-04 19:43 ` kargl at gcc dot gnu dot org 2009-01-04 19:46 ` kargl at gcc dot gnu dot org [this message] 2009-01-04 19:47 ` [Bug libgomp/38724] Segfault caused by derived-type " kargl at gcc dot gnu dot org 2009-01-04 21:31 ` jakub at gcc dot gnu dot org 2009-01-05 2:32 ` sgk at troutmask dot apl dot washington dot edu
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=20090104194602.12116.qmail@sourceware.org \ --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).