public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "Joost.VandeVondele at mat dot ethz.ch" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug sanitizer/59286] segfault in  __sanitizer::StackDepotGet
Date: Tue, 26 Nov 2013 07:25:00 -0000	[thread overview]
Message-ID: <bug-59286-4-ybJRdqsStz@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-59286-4@http.gcc.gnu.org/bugzilla/>

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59286

--- Comment #4 from Joost VandeVondele <Joost.VandeVondele at mat dot ethz.ch> ---
(In reply to Kostya Serebryany from comment #3)
> Can you post the exact command line to reproduce the failure? 
> (We should have CP2K sources somewhere)

The exact command line is rather easy:

cd cp2k/tests/QS/regtest-hybrid-1
export OMP_NUM_THREADS=4 ; ../../../exe/test_tsan/cp2k.ssmp H2O-hybrid-pbe0.inp

However, building a tsan instrumented CP2K is non-trivial, as it requires
libgomp to be built with tsan (see
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55561#c15 for a howto), and some of
the dependent libraries must be built with tsan as well. I'm happy to help, but
could take some time. Should I post detailed instructions?


Meanwhile another CP2K input fails with:

Unexpected mmap in InternalAllocator!


  parent reply	other threads:[~2013-11-26  7:25 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-25 15:13 [Bug sanitizer/59286] New: " Joost.VandeVondele at mat dot ethz.ch
2013-11-26  6:58 ` [Bug sanitizer/59286] " Joost.VandeVondele at mat dot ethz.ch
2013-11-26  7:12 ` kcc at gcc dot gnu.org
2013-11-26  7:25 ` Joost.VandeVondele at mat dot ethz.ch [this message]
2013-11-26 10:44 ` kcc at gcc dot gnu.org
2013-11-26 11:57 ` Joost.VandeVondele at mat dot ethz.ch
2013-11-26 13:36 ` kcc at gcc dot gnu.org
2013-11-26 13:48 ` Joost.VandeVondele at mat dot ethz.ch
2013-11-26 15:06 ` Joost.VandeVondele at mat dot ethz.ch
2024-03-16 21:29 ` pinskia at gcc dot gnu.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=bug-59286-4-ybJRdqsStz@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: link
Be 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).