public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "aburgess at broadcom dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug fortran/11104] gdb 7.0 does not print two dimensional Fortran arrays correctly.
Date: Thu, 16 Sep 2010 08:45:00 -0000 [thread overview]
Message-ID: <20100916084531.16845.qmail@sourceware.org> (raw)
In-Reply-To: <20091217184247.11104.at_gdb@mathalacarte.com>
------- Additional Comments From aburgess at broadcom dot com 2010-09-16 08:45 -------
Created an attachment (id=4987)
--> (http://sourceware.org/bugzilla/attachment.cgi?id=4987&action=view)
Updated testcase
Finally got the Fortran tests running, slight update to the test case.
--
What |Removed |Added
----------------------------------------------------------------------------
Attachment #4977 is|0 |1
obsolete| |
http://sourceware.org/bugzilla/show_bug.cgi?id=11104
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
next prev parent reply other threads:[~2010-09-16 8:45 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-17 18:42 [Bug fortran/11104] New: " at_gdb at mathalacarte dot com
2010-01-26 16:09 ` [Bug fortran/11104] " at_gdb at mathalacarte dot com
2010-05-31 9:49 ` fenixk19 at mail dot ru
2010-09-12 14:43 ` aburgess at broadcom dot com
2010-09-12 14:53 ` aburgess at broadcom dot com
2010-09-16 8:03 ` aburgess at broadcom dot com
2010-09-16 8:45 ` aburgess at broadcom dot com [this message]
[not found] <bug-11104-4717@http.sourceware.org/bugzilla/>
2010-10-19 8:31 ` aburgess at broadcom dot com
2010-10-19 15:11 ` aburgess at broadcom dot com
2010-10-19 15:12 ` aburgess at broadcom dot com
2011-01-12 16:16 ` cvs-commit at gcc dot gnu.org
2011-01-12 16:22 ` jan.kratochvil at redhat dot com
2011-04-05 14:44 ` smirta at mail dot ru
2011-04-21 11:25 ` smirta at mail dot ru
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=20100916084531.16845.qmail@sourceware.org \
--to=sourceware-bugzilla@sourceware.org \
--cc=gdb-prs@sourceware.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).