From: "Hicham Mouline" <hicham@mouline.org>
To: "'Jan Kratochvil'" <jan.kratochvil@redhat.com>
Cc: <gdb@sourceware.org>
Subject: RE: gomp status
Date: Mon, 30 Aug 2010 23:21:00 -0000 [thread overview]
Message-ID: <000d01cb489a$0b8c2b10$22a48130$@org> (raw)
In-Reply-To: <20100830175734.GA11759@host1.dyn.jankratochvil.net>
> -----Original Message-----
> From: Jan Kratochvil [mailto:jan.kratochvil@redhat.com]
> Sent: 30 August 2010 18:58
> To: Hicham Mouline
> Cc: gdb@sourceware.org
> Subject: Re: gomp status
>
> On Fri, 27 Aug 2010 17:28:46 +0200, Hicham Mouline wrote:
> > What is the status of debugging parallel openmp regions with gdb?
> > In particular the ability to display thread-specific values of
> variables?
>
> There is fix of OMP stepping:
> http://cvs.fedoraproject.org/viewvc/rpms/gdb/devel/gdb-bz533176-
> fortran-omp-step.patch?content-type=text%2Fplain&view=co
>
> and it worked some way during my tests. But I cannot report on more
> details
> offhand. There is a generated new function for the parallel block
> which
> should have debug info for all its local variables.
>
>
> Regards,
> Jan
I've used gdb 7.1.26 to debug a binary built with g++4.3.3 (C++) and the
libgomp that comes with it.
I can step in/over properly inside a parallel block but I can't
display/watch variables inside it.
It says "symbol unavailable" or something like that.
Variables just outside the // block are displayed fine,
Is the fix you mention above fortran-specific? Is it in 7.1.x?
regards,
next prev parent reply other threads:[~2010-08-30 23:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-27 15:28 Hicham Mouline
2010-08-30 17:50 ` Michael Snyder
2010-08-30 17:57 ` Jan Kratochvil
2010-08-30 23:21 ` Hicham Mouline [this message]
2010-08-31 3:42 ` Jan Kratochvil
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='000d01cb489a$0b8c2b10$22a48130$@org' \
--to=hicham@mouline.org \
--cc=gdb@sourceware.org \
--cc=jan.kratochvil@redhat.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