From: Thomas Koenig <tkoenig@netcologne.de>
To: dhumieres.dominique@free.fr
Cc: fortran@gcc.gnu.org
Subject: Re: Update on shared memory coarrays
Date: Tue, 22 Dec 2020 16:10:54 +0100 [thread overview]
Message-ID: <ac7d029c-54a2-dcd3-4676-d4e514bb2e53@netcologne.de> (raw)
In-Reply-To: <79fdfc28ee95e21ba173dad5780b4e02@free.fr>
Hi Dominique,
> Indeed! I can try to do some debugging under supervision.
> Could you please tell me where to start?
Thanks for your offer.
The first thing to do would be to see where it hangs. Generating
a syscall trace (by whatever tool is used on MacOS, dtrace? ktrace?)
would be a first step.
A next step would be to compile a program with debug info and
run it under a debugger, then see where it hangs.
I'm not sure - do you use gdb on your system? If you do,
the following lines in your .gdbinit
define better_mp_debug
set detach-on-fork off
set schedule-multiple on
set follow-fork-mode parent
set non-stop on
set target-async on
set print symbol-loading off
end
will give you a macro "better_mp_debug" which will ease debugging
of forked processes enormously.
My lack of experience with MacOS extends to which tools to use
for debugging, unfortunately.
Best regards
Thomas
next prev parent reply other threads:[~2020-12-22 15:10 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-29 19:09 dhumieres.dominique
2020-11-30 6:21 ` Thomas Koenig
2020-11-30 15:41 ` dhumieres.dominique
2020-11-30 22:13 ` Thomas Koenig
2020-12-02 17:41 ` dhumieres.dominique
2020-12-03 7:27 ` Thomas Koenig
2020-12-21 12:24 ` dhumieres.dominique
2020-12-21 13:04 ` Thomas Koenig
2020-12-22 12:28 ` dhumieres.dominique
2020-12-22 15:10 ` Thomas Koenig [this message]
2020-12-22 16:12 ` Paul Richard Thomas
2020-12-23 9:09 ` Thomas Koenig
2020-12-23 9:38 ` Paul Richard Thomas
2020-12-23 10:47 ` Thomas Koenig
2020-12-26 12:10 ` Paul Richard Thomas
2020-12-26 13:01 ` Thomas Koenig
2020-12-27 15:38 ` Thomas Koenig
2020-12-23 16:42 ` Nicolas König
2020-12-23 17:25 ` dhumieres.dominique
2020-12-27 17:10 ` Nicolas König
2021-01-01 13:51 ` dhumieres.dominique
2021-01-01 16:16 ` Thomas Koenig
2021-01-01 16:41 ` dhumieres.dominique
2021-01-02 20:45 ` Thomas Koenig
2021-01-02 20:55 ` Iain Sandoe
2021-01-02 21:43 ` Thomas Koenig
2021-01-02 22:37 ` Nicolas König
2021-01-02 21:44 ` Iain Sandoe
2021-01-02 22:09 ` Iain Sandoe
2021-01-03 10:46 ` Iain Sandoe
2021-01-03 14:54 ` Iain Sandoe
2021-01-03 15:42 ` Iain Sandoe
2021-01-03 21:53 ` Thomas Koenig
2021-01-04 2:34 ` Iain Sandoe
2021-01-04 18:54 ` Nicolas König
2021-01-05 13:11 ` Iain Sandoe
2021-01-05 13:23 ` Iain Sandoe
2021-01-05 13:27 ` Thomas Koenig
2021-01-05 13:34 ` Iain Sandoe
2021-01-05 14:54 ` Nicolas König
2021-01-05 14:28 ` Iain Sandoe
2021-01-05 15:45 ` Nicolas König
[not found] ` <BAD6EA1D-BB9F-4905-ADD1-76FA1D6B9591@sandoe.co.uk>
2021-01-05 17:11 ` Nicolas König
2021-01-06 16:56 ` Iain Sandoe
-- strict thread matches above, loose matches on Subject: below --
2020-11-29 13:10 Nicolas König
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=ac7d029c-54a2-dcd3-4676-d4e514bb2e53@netcologne.de \
--to=tkoenig@netcologne.de \
--cc=dhumieres.dominique@free.fr \
--cc=fortran@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).