public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "DBarto at visionpro dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/58104] std::call_once appears to fail on standard code Date: Thu, 08 Aug 2013 16:20:00 -0000 [thread overview] Message-ID: <bug-58104-4-7SrYIHlRq4@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-58104-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58104 --- Comment #3 from DBarto at visionpro dot com --- /opt/local/bin/g++-mp-4.7 -std=c++11 -Wall -Wextra -pthread -g use_once.cpp -o use_once ./use_once 571_ ./use_once Segmentation fault: 11 gdb use_once (gdb) r Starting program: /Users/barto/mvp/trunk/unit_test/use_once Reading symbols for shared libraries +++.............................. done Program received signal EXC_BAD_ACCESS, Could not access memory. Reason: 13 at address: 0x0000000000000000 [Switching to process 22829 thread 0x1203] 0x0000000100074b20 in __once_proxy () (gdb) where #0 0x0000000100074b20 in __once_proxy () #1 0x00007fff8f7e0ff0 in pthread_once () #2 0x0000000100001165 in __gthread_once (__once=0x1000055e0, __func=0x100074b10 <__once_proxy>) at gthr-default.h:718 #3 0x000000010000142d in call_once<do_once()::<lambda()> > (__once=@0x1000055e0, __f=@0x100293e6f) at mutex:822 #4 0x0000000100001247 in do_once () at use_once.cpp:47 #5 0x0000000100002a29 in _ZNSt12_Bind_simpleIFPFvvEvEE9_M_invokeIIEEEvSt12_Index_tupleIIXspT_EEE (this=0x100303aa0) at functional:1598 #6 0x0000000100002979 in std::_Bind_simple<void (*()())()>::operator() (this=0x100303aa0) at functional:1586 #7 0x0000000100002912 in std::thread::_Impl<std::_Bind_simple<void (*()())()> >::_M_run (this=0x100303a88) at thread:115 #8 0x00000001000754b0 in execute_native_thread_routine () #9 0x00007fff8f7cc1e1 in thread_start () On Aug 8, 2013, at 9:10 AM, redi at gcc dot gnu.org <gcc-bugzilla@gcc.gnu.org> wrote: > http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58104 > > --- Comment #1 from Jonathan Wakely <redi at gcc dot gnu.org> --- > Works for me. > > Are you using the -pthread flag? > > You haven't actually said what fails, what fails to execute? > > -- > You are receiving this mail because: > You reported the bug.
next prev parent reply other threads:[~2013-08-08 16:20 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-08-08 16:03 [Bug libstdc++/58104] New: " barto at visionpro dot com 2013-08-08 16:10 ` [Bug libstdc++/58104] " redi at gcc dot gnu.org 2013-08-08 16:15 ` DBarto at visionpro dot com 2013-08-08 16:20 ` DBarto at visionpro dot com [this message] 2013-08-08 18:23 ` barto at visionpro dot com 2013-08-08 23:53 ` redi at gcc dot gnu.org 2013-08-09 0:03 ` barto at visionpro dot com 2013-08-09 9:06 ` [Bug target/58104] " redi at gcc dot gnu.org 2013-08-09 15:29 ` barto at visionpro dot com
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=bug-58104-4-7SrYIHlRq4@http.gcc.gnu.org/bugzilla/ \ --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).