public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "steven at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/24527] derived types not displayed correctly with gdb
Date: Sat, 14 Oct 2006 15:16:00 -0000	[thread overview]
Message-ID: <20061014151556.22144.qmail@sourceware.org> (raw)
In-Reply-To: <bug-24527-10391@http.gcc.gnu.org/bugzilla/>



------- Comment #4 from steven at gcc dot gnu dot org  2006-10-14 15:15 -------
This works with the patch I mentioned in comment #3.  That patch is in the GDB
source tree since 2006-02-24, so this is "fixed" in GDB 6.5.  On the GCC side
we seem to do the right thing for scalar components.  For array components
obviously we don't but there is a separate bug about that.

So I'm calling this FIXED.


-- 

steven at gcc dot gnu dot org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|ASSIGNED                    |RESOLVED
         Resolution|                            |FIXED


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=24527


      parent reply	other threads:[~2006-10-14 15:16 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-25 19:58 [Bug fortran/24527] New: derived types not displayed correctly tkoenig at gcc dot gnu dot org
2005-10-27 23:24 ` [Bug fortran/24527] derived types not displayed correctly with gdb pinskia at gcc dot gnu dot org
2005-10-28  4:39 ` woodzltc at sources dot redhat dot com
2006-10-14 14:47 ` steven at gcc dot gnu dot org
2006-10-14 15:16 ` steven at gcc dot gnu dot org [this message]

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=20061014151556.22144.qmail@sourceware.org \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@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).