public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "bruno at clisp dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libgomp/28468] OpenMP-parallelized program crashes when OMP_NUM_THREADS > 1 Date: Tue, 07 Nov 2006 14:36:00 -0000 [thread overview] Message-ID: <20061107143620.29469.qmail@sourceware.org> (raw) In-Reply-To: <bug-28468-128@http.gcc.gnu.org/bugzilla/> ------- Comment #1 from bruno at clisp dot org 2006-11-07 14:36 ------- It's still reproducible with gcc-4.2-20061031: $ export OMP_NUM_THREADS=2 $ gdb a.out GNU gdb 6.4 Copyright 2005 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "i686-pc-linux-gnu"...Using host libthread_db library "/lib/libthread_db.so.1". (gdb) run Starting program: /dev/shm/a.out [Thread debugging using libthread_db enabled] [New Thread 16384 (LWP 4983)] [New Thread 32769 (LWP 4984)] [New Thread 16386 (LWP 4985)] Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 16386 (LWP 4985)] gomp_iter_dynamic_next (pstart=0xbf7ffa94, pend=0xbf7ffa98) at ../../../gcc-4.2-20061031/libgomp/iter.c:189 189 start = ws->next; (gdb) where #0 gomp_iter_dynamic_next (pstart=0xbf7ffa94, pend=0xbf7ffa98) at ../../../gcc-4.2-20061031/libgomp/iter.c:189 #1 0x4001ca78 in gomp_loop_dynamic_next (istart=0xbf7ffa94, iend=0xbf7ffa98) at ../../../gcc-4.2-20061031/libgomp/loop.c:248 #2 0x080486ed in main.omp_fn.0 () #3 0x4001de5d in gomp_thread_start (xdata=0xbfffe580) at ../../../gcc-4.2-20061031/libgomp/team.c:108 #4 0x4003bfe6 in pthread_start_thread (arg=0xbf7ffbe0) at manager.c:310 #5 0x4003c07f in pthread_start_thread_event (arg=0xbf7ffbe0) at manager.c:334 #6 0x4014e0aa in clone () from /lib/libc.so.6 -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=28468
next prev parent reply other threads:[~2006-11-07 14:36 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2006-07-24 14:19 [Bug libgomp/28468] New: " bruno at clisp dot org 2006-11-07 14:36 ` bruno at clisp dot org [this message] 2006-11-15 9:45 ` [Bug libgomp/28468] " jakub at gcc dot gnu dot org 2006-11-15 13:39 ` bruno at clisp dot org 2007-02-07 13:35 ` jakub at gcc dot gnu dot org 2007-02-07 13:39 ` jakub at gcc dot gnu dot org 2007-10-23 15:41 ` rth at gcc dot gnu dot org 2008-03-10 16:10 ` jakub at gcc dot gnu dot org
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=20061107143620.29469.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).