Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Andrew Burgess <andrew.burgess@embecosm.com>
To: gdb-patches@sourceware.org
Subject: Re: [PATCH 1/7] gdb: Add new -n flag to some info commands
Date: Tue, 27 Aug 2019 15:27:00 -0000	[thread overview]
Message-ID: <20190827152719.GP6076@embecosm.com> (raw)
In-Reply-To: <83h863gas2.fsf@gnu.org>

* Eli Zaretskii <eliz@gnu.org> [2019-08-26 19:18:53 +0300]:

> > Date: Mon, 26 Aug 2019 16:52:00 +0100
> > From: Andrew Burgess <andrew.burgess@embecosm.com>
> > Cc: gdb-patches@sourceware.org, Richard.Bunt@arm.com
> > 
> > +  ** The "info variables", "info functions", and "whereis" commands
> > +     now take a '-n' flag that excludes non-debug symbols (symbols
> > +     from the symbol table, not from the debug info such as DWARf)
>                                                                    ^
> A typo.
> 
> Other than that, the documentation parts are OK.
> 
> Thanks.

Thanks,

This patch is now pushed.

Andrew


  reply	other threads:[~2019-08-27 15:27 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-27 16:22 [PATCH 0/7] Fortran info types, info modules, info module Andrew Burgess
2019-07-27 16:22 ` [PATCH 3/7] gdb/fortran: Include module variables in 'info variables' output Andrew Burgess
2019-07-27 16:22 ` [PATCH 2/7] gdb: Add an is_declaration field to each symbol Andrew Burgess
2019-07-29 20:21   ` Tom Tromey
2019-07-30 21:00     ` Andrew Burgess
2019-07-27 16:23 ` [PATCH 1/7] gdb: Add new -n flag to some info commands Andrew Burgess
2019-07-27 16:41   ` Eli Zaretskii
2019-07-30 21:02     ` Andrew Burgess
2019-07-31 14:51       ` Eli Zaretskii
2019-08-26 15:52         ` Andrew Burgess
2019-08-26 16:19           ` Eli Zaretskii
2019-08-27 15:27             ` Andrew Burgess [this message]
2019-08-28 15:13               ` [committed][gdb/testsuite] Fix info-var.exp for debug info from other files Tom de Vries
2019-07-29 20:23   ` [PATCH 1/7] gdb: Add new -n flag to some info commands Tom Tromey
2019-07-27 16:23 ` [PATCH 6/7] gdb/fortran: Add new 'info modules' command Andrew Burgess
2019-07-27 16:45   ` Eli Zaretskii
2019-07-29 20:30   ` Tom Tromey
2019-07-27 16:23 ` [PATCH 7/7] gdb: Add new commands to list module variables and functions Andrew Burgess
2019-07-27 17:06   ` Eli Zaretskii
2019-07-27 16:23 ` [PATCH 4/7] gdb/fortran: Implement la_print_typedef for Fortran Andrew Burgess
2019-08-28 12:37   ` Andrew Burgess
2019-07-27 16:23 ` [PATCH 5/7] gdb/fortran: Don't include module symbols when searching for types Andrew Burgess
2019-08-28 12:37   ` Andrew Burgess
2019-08-29  9:09     ` Tom de Vries
2019-08-29 11:45       ` Tom de Vries
2019-08-29 12:47     ` [committed][gdb/testsuite] Fix gdb.fortran/info-types.exp regexp Tom de Vries

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=20190827152719.GP6076@embecosm.com \
    --to=andrew.burgess@embecosm.com \
    --cc=gdb-patches@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: 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