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 v3 5/6] Fortran: Enable setting breakpoint on nested functions.
Date: Mon, 04 Sep 2017 09:22:00 -0000 [thread overview]
Message-ID: <20170904092212.GA8425@1170ee0b50d5> (raw)
In-Reply-To: <1502449611-8865-6-git-send-email-tim.wiederhake@intel.com>
On 17-08-11 13:06:50, Tim Wiederhake wrote:
> From: Bernhard Heckel <bernhard.heckel@intel.com>
>
> Like in Ada, we want to be able to set a breakpoint on nested functions,
> called "contained routines" in Fortran.
>
> xxxx-yy-zz Bernhard Heckel <bernhard.heckel@intel.com>
>
> gdb/ChangeLog:
> * dwarf2read.c (add_partial_symbol): Enable for Fortran as well.
> (new_symbol_full): Same.
> (add_partial_subprogram): Check for subprogram tag.
>
> gdb/testsuite/ChangeLog:
> * gdb.fortran/nested-funcs.exp: Set breakpoint on contained routines.
Patch is good to me.
--
Yao (é½å°§)
next prev parent reply other threads:[~2017-09-04 9:22 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-11 11:07 [PATCH v3 0/6] Some Fortran Patches Tim Wiederhake
2017-08-11 11:07 ` [PATCH v3 4/6] Dwarf: Fortran, support DW_TAG_entry_point Tim Wiederhake
2017-09-04 8:37 ` Yao Qi
2017-08-11 11:07 ` [PATCH v3 2/6] Fortran: Accessing fields of inherited types via fully qualified name Tim Wiederhake
2017-08-11 11:07 ` [PATCH v3 6/6] Fortran: Nested functions, add scope parameter Tim Wiederhake
2017-09-04 9:58 ` Yao Qi
2017-09-08 12:13 ` Wiederhake, Tim
2017-08-11 11:07 ` [PATCH v3 3/6] Fortran: Ptype, print type extension Tim Wiederhake
2017-08-23 11:05 ` Yao Qi
2017-08-24 12:36 ` Wiederhake, Tim
2017-08-11 11:07 ` [PATCH v3 5/6] Fortran: Enable setting breakpoint on nested functions Tim Wiederhake
2017-09-04 9:22 ` Yao Qi [this message]
2017-08-11 11:07 ` [PATCH v3 1/6] DWARF: Don't add nameless modules to partial symbol table Tim Wiederhake
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=20170904092212.GA8425@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