From: Thomas Koenig <tkoenig@netcologne.de>
To: "N.M. Maclaren" <nmm1@cam.ac.uk>,
Paul Richard Thomas <paul.richard.thomas@gmail.com>
Cc: "fortran@gcc.gnu.org" <fortran@gcc.gnu.org>
Subject: Re: Teaching and debugging OpenMP in gfortran (or otherwise!)
Date: Sat, 15 Sep 2018 16:22:00 -0000 [thread overview]
Message-ID: <9bb6ab97-2140-e2eb-3310-6f9983f4b6ed@netcologne.de> (raw)
In-Reply-To: <Prayer.1.3.5.1809151652220.31383@hermes-2.csi.cam.ac.uk>
Am 15.09.2018 um 17:52 schrieb N.M. Maclaren:
> I am specifically asking about tools for
> automatic checking for race conditions - most of my course is about
> writing OpenMP that actually works, and it goes into great length about
> how hard it is to debug.
I have not debugged OpenMP myself, but for pthread - based code (the
async I/O stuff) valgrind has been invaluable. It helped Nicolas and
me to debug a one in 20000 occurrence of a deadlock...
Specifically, try to use
valgrind --tool=helgrind
and
valgrind --tool=drd
and watch the bugs come crawling out :-)
Regards
Thomas
next prev parent reply other threads:[~2018-09-15 16:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-14 8:06 [PATCH][libgfortran] Fix uninitialized variable use in fallback_access Kyrill Tkachov
2018-09-14 9:11 ` Paul Richard Thomas
2018-09-15 12:02 ` Teaching and debugging OpenMP in gfortran (or otherwise!) N.M. Maclaren
2018-09-15 15:30 ` Paul Richard Thomas
2018-09-15 15:52 ` N.M. Maclaren
2018-09-15 16:22 ` Thomas Koenig [this message]
2018-09-15 18:10 ` N.M. Maclaren
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=9bb6ab97-2140-e2eb-3310-6f9983f4b6ed@netcologne.de \
--to=tkoenig@netcologne.de \
--cc=fortran@gcc.gnu.org \
--cc=nmm1@cam.ac.uk \
--cc=paul.richard.thomas@gmail.com \
/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).