From: Eli Zaretskii <eliz@gnu.org>
To: "Maciej W. Rozycki" <macro@embecosm.com>
Cc: gdb-patches@sourceware.org, richard.bunt@linaro.org
Subject: Re: [PATCH v2 3/3] GDB: Add `info main' command
Date: Tue, 28 Mar 2023 22:01:36 +0300 [thread overview]
Message-ID: <83r0t87l9r.fsf@gnu.org> (raw)
In-Reply-To: <alpine.DEB.2.20.2303281942180.15477@tpp.orcam.me.uk> (macro@embecosm.com)
> Date: Tue, 28 Mar 2023 19:49:02 +0100 (BST)
> From: "Maciej W. Rozycki" <macro@embecosm.com>
> cc: Richard Bunt <richard.bunt@linaro.org>
>
> From: Richard Bunt <richard.bunt@linaro.org>
>
> Allow consumers of GDB to extract the name of the main method. This is
> most useful for Fortran programs which have a variable main method.
>
> Used by both MAP and DDT e.g. it is used to detect the presence of debug
> information.
>
> Co-Authored-By: Maciej W. Rozycki <macro@embecosm.com>
> ---
> Changes from v1:
>
> - Add documentation pieces.
> ---
> gdb/NEWS | 3 ++
> gdb/doc/gdb.texinfo | 6 ++++
> gdb/symtab.c | 11 ++++++++
> gdb/testsuite/gdb.fortran/info-main.exp | 42 ++++++++++++++++++++++++++++++++
> gdb/testsuite/gdb.fortran/info-main.f90 | 19 ++++++++++++++
> 5 files changed, 81 insertions(+)
Thanks, the documentation parts are OK.
Reviewed-By: Eli Zaretskii <eliz@gnu.org>
prev parent reply other threads:[~2023-03-28 19:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-28 18:45 [PATCH v2 0/3] Fixes and improvements for the starting function Maciej W. Rozycki
2023-03-28 18:48 ` [PATCH v2 1/3] GDB: Favor full symbol main name for backtrace stop Maciej W. Rozycki
2023-03-28 18:48 ` [PATCH v2 2/3] GDB: Bring back the handling of DW_CC_program Maciej W. Rozycki
2023-03-28 19:26 ` Tom Tromey
2023-03-29 17:54 ` Maciej W. Rozycki
2023-03-28 18:49 ` [PATCH v2 3/3] GDB: Add `info main' command Maciej W. Rozycki
2023-03-28 19:01 ` Eli Zaretskii [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=83r0t87l9r.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=macro@embecosm.com \
--cc=richard.bunt@linaro.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).