public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <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: Wed, 12 Jan 2011 16:16:00 -0000 [thread overview]
Message-ID: <bug-11104-4717-2V5Jks7nMB@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-11104-4717@http.sourceware.org/bugzilla/>
http://sourceware.org/bugzilla/show_bug.cgi?id=11104
--- Comment #10 from cvs-commit at gcc dot gnu.org <cvs-commit at gcc dot gnu.org> 2011-01-12 16:16:33 UTC ---
CVSROOT: /cvs/src
Module name: src
Changes by: jkratoch@sourceware.org 2011-01-12 16:16:25
Modified files:
gdb : ChangeLog dwarf2read.c eval.c
gdb/testsuite : ChangeLog
Added files:
gdb/testsuite/gdb.fortran: multi-dim.exp multi-dim.f90
Log message:
gdb/
PR fortran/11104 and DWARF unbound arrays detection.
* dwarf2read.c (read_subrange_type): Set zero length on unspecified
upper bound. Set TYPE_HIGH_BOUND_UNDEFINED if not language_ada on
unspecified upper bound.
* eval.c (evaluate_subexp_standard) <multi_f77_subscript>: Remove
variables array_size_array, tmp_type and offset_item. New variable
array. Remove call to f77_get_upperbound. New variables array_type
and index. Call value_subscripted_rvalue for each dimenasion. Remove
the final call to deprecated_set_value_type.
gdb/testsuite/
PR fortran/11104 and DWARF unbound arrays detection.
* gdb.fortran/multi-dim.exp: New file.
* gdb.fortran/multi-dim.f90: New file.
Patches:
http://sourceware.org/cgi-bin/cvsweb.cgi/src/gdb/ChangeLog.diff?cvsroot=src&r1=1.12463&r2=1.12464
http://sourceware.org/cgi-bin/cvsweb.cgi/src/gdb/dwarf2read.c.diff?cvsroot=src&r1=1.494&r2=1.495
http://sourceware.org/cgi-bin/cvsweb.cgi/src/gdb/eval.c.diff?cvsroot=src&r1=1.145&r2=1.146
http://sourceware.org/cgi-bin/cvsweb.cgi/src/gdb/testsuite/ChangeLog.diff?cvsroot=src&r1=1.2549&r2=1.2550
http://sourceware.org/cgi-bin/cvsweb.cgi/src/gdb/testsuite/gdb.fortran/multi-dim.exp.diff?cvsroot=src&r1=NONE&r2=1.1
http://sourceware.org/cgi-bin/cvsweb.cgi/src/gdb/testsuite/gdb.fortran/multi-dim.f90.diff?cvsroot=src&r1=NONE&r2=1.1
--
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
next prev parent reply other threads:[~2011-01-12 16:16 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[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 [this message]
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
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
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=bug-11104-4717-2V5Jks7nMB@http.sourceware.org/bugzilla/ \
--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).