public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "burnus at gmx dot de" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug fortran/15353] New: ptype/whatis doesn't handle DW_TAG_namelist Date: Tue, 09 Apr 2013 22:20:00 -0000 [thread overview] Message-ID: <bug-15353-4717@http.sourceware.org/bugzilla/> (raw) http://sourceware.org/bugzilla/show_bug.cgi?id=15353 Bug #: 15353 Summary: ptype/whatis doesn't handle DW_TAG_namelist Product: gdb Version: 7.5 Status: NEW Severity: normal Priority: P2 Component: fortran AssignedTo: unassigned@sourceware.org ReportedBy: burnus@gmx.de CC: jan.kratochvil@redhat.com, sanimir.agovic@intel.com Classification: Unclassified Vaguely related to bug 15209. Example: integer :: aa,bb namelist /nml/ aa aa = 5 end generates <2><1a9>: Abbrev Number: 3 (DW_TAG_namelist) <1aa> DW_AT_name : nml <1ae> DW_AT_sibling : <0x1b8> <3><1b2>: Abbrev Number: 4 (DW_TAG_namelist_item) <1b3> DW_AT_namelist_items: <0x1b8> <2><1b8>: Abbrev Number: 5 (DW_TAG_variable) <1b9> DW_AT_name : aa I would expect that gdb prints something like type = namelist /nml/ aa Currently, it does not recognize "nml". DW_TAG_namelist is part of DWARF2. See also: http://gcc.gnu.org/bugzilla/show_bug.cgi?id=37132 http://gcc.gnu.org/ml/gcc-patches/2013-04/msg00560.html -- 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 reply other threads:[~2013-04-09 22:20 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-04-09 22:20 burnus at gmx dot de [this message] 2013-12-05 0:55 ` [Bug fortran/15353] " burnus at gmx dot de 2022-02-25 17:01 ` tromey at sourceware dot org
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-15353-4717@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: linkBe 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).