From: Yao Qi <qiyaoltc@gmail.com>
To: Tim Wiederhake <tim.wiederhake@intel.com>
Cc: gdb-patches@sourceware.org, Bernhard Heckel <bernhard.heckel@intel.com>
Subject: Re: [PATCH 1/6] DWARF: Don't add nameless modules to partial symbol table.
Date: Mon, 31 Jul 2017 22:09:00 -0000 [thread overview]
Message-ID: <20170731220938.GB8039@1170ee0b50d5> (raw)
In-Reply-To: <1500629040-12972-2-git-send-email-tim.wiederhake@intel.com>
On 17-07-21 11:23:55, Tim Wiederhake wrote:
> From: Bernhard Heckel <bernhard.heckel@intel.com>
>
> A name for BLOCK DATA in Fortran is optional. If no name has been assigned,
> GDB will crash during read-in of DWARF when BLOCK DATA is represented via
> DW_TAG_module.
What is your Fortran compiler? I used gfortran 4.9.4, it doesn't generate
DW_TAG_module in debug information. So, I run block-data.exp with
unpatched GDB, all tests pass.
>
> BLOCK DATA is used for one-time initialization of non-pointer variables in
> named common blocks.
>
> xxxx-yy-zz Bernhard Heckel <bernhard.heckel@intel.com>
>
> gdb/ChangeLog:
> * dwarf2read.c (add_partial_symbol): Skip nameless modules.
>
> gdb/testsuite/ChangeLog:
> * gdb.fortran/block-data.f: New file.
> * gdb.fortran/block-data.exp: New file.
>
--
Yao (é½å°§)
next prev parent reply other threads:[~2017-07-31 22:09 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-21 9:25 [PATCH 0/6] Some Fortran patches Tim Wiederhake
2017-07-21 9:25 ` [PATCH 6/6] Fortran: Nested functions, add scope parameter Tim Wiederhake
2017-07-21 9:25 ` [PATCH 1/6] DWARF: Don't add nameless modules to partial symbol table Tim Wiederhake
2017-07-31 22:09 ` Yao Qi [this message]
2017-08-01 12:47 ` Wiederhake, Tim
2017-08-02 11:16 ` Yao Qi
2017-08-04 11:03 ` Wiederhake, Tim
2017-07-21 9:25 ` [PATCH 2/6] Fortran: Accessing fields of inherited types via fully qualified name Tim Wiederhake
2017-07-21 9:25 ` [PATCH 3/6] Fortran: Ptype, print type extension Tim Wiederhake
2017-08-07 12:08 ` Yao Qi
2017-07-21 9:25 ` [PATCH 4/6] Dwarf: Fortran, support DW_TAG_entry_point Tim Wiederhake
2017-07-31 22:20 ` Yao Qi
2017-08-02 13:14 ` Yao Qi
[not found] ` <9676A094AF46E14E8265E7A3F4CCE9AF5AC20F28@irsmsx105.ger.corp.intel.com>
2017-08-07 8:46 ` Wiederhake, Tim
2017-08-07 11:29 ` Yao Qi
2017-08-08 14:36 ` Wiederhake, Tim
2017-07-21 9:25 ` [PATCH 5/6] Fortran: Enable setting breakpoint on nested functions Tim Wiederhake
2017-07-28 8:19 ` [PATCH 0/6] Some Fortran patches Wiederhake, Tim
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=20170731220938.GB8039@1170ee0b50d5 \
--to=qiyaoltc@gmail.com \
--cc=bernhard.heckel@intel.com \
--cc=gdb-patches@sourceware.org \
--cc=tim.wiederhake@intel.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