From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: Lurkos <lurkos.usenet@gmail.com>
Cc: gdb@sources.redhat.com
Subject: Re: cannot print allocatable arrays
Date: Fri, 23 Sep 2011 15:26:00 -0000 [thread overview]
Message-ID: <20110923152535.GA29312@host1.jankratochvil.net> (raw)
In-Reply-To: <20110923144610.10149.52279.XPN@L622243018051.user.x-privat.org>
On Fri, 23 Sep 2011 16:46:10 +0200, Lurkos wrote:
> I'm using gdb 7.0.1-debian and gfortran 4.4.5 on Debian squeeze amd64.
>
> I'm not able to print arrays that are declared as allocatable.
This works in archer-jankratochvil-vla branch
http://sourceware.org/gdb/wiki/ArcherBranchManagement
and Fedora GDBs; even there it has some limitations for complicated data
structures but in general it works.
Not sure when it gets merged, it needs to be mostly rewritten. There are
AFAIK also some independent efforts for this feature for GDB.
Regards,
Jan
next prev parent reply other threads:[~2011-09-23 15:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-23 15:20 Lurkos
2011-09-23 15:26 ` Jan Kratochvil [this message]
2011-10-04 19:00 ` Lurkos
2011-10-04 23:46 ` Lurkos
2011-09-23 15:32 ` Joachim Protze
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=20110923152535.GA29312@host1.jankratochvil.net \
--to=jan.kratochvil@redhat.com \
--cc=gdb@sources.redhat.com \
--cc=lurkos.usenet@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