From: Philippe Waroquiers <philippe.waroquiers@skynet.be>
To: gdb-patches@sourceware.org
Subject: PING^2 Re: [RFAv3 0/5] info [args|functions|locals|variables] [-q] [-t TYPEREGEXP] [NAMEREGEXP]
Date: Thu, 11 Oct 2018 19:56:00 -0000 [thread overview]
Message-ID: <1539287771.2137.4.camel@skynet.be> (raw)
In-Reply-To: <20180923214209.985-1-philippe.waroquiers@skynet.be>
Ping ?
Thanks
On Sun, 2018-09-23 at 23:42 +0200, Philippe Waroquiers wrote:
> [RFAv3 0/5] info [args|functions|locals|variables] [-q] [-t TYPEREGEXP] [NAMEREGEXP]
>
> RFAv3, handling the comments of Tom and Eli about RFAv2.
> --------------------------------------------------------
> * code changes:
> - reworked extract_arg_maybe_quoted to have it working the same way
> as gdb_argv. In another patch series, I will evaluate more in
> detail handling quoting/escaping inside extract_arg, by analysing
> all callers.
> - fixed (and tested) regression when NAMEREGEXP arg contains spaces.
> - replaced INFO_PRINT_ARGS_HELP by function info_print_args_help
> to make this gettext friendly.
>
> - instead of preg/treg regexp new arguments to iterate_over_block_arg_vars
> and iterate_over_block_local_vars, have preg/treg being part
> of the opaque cb_data, and do filtering inside do_print_variable_and_value.
> - no need anymore to include gdb_regex.h in various files or stack.h.
> - used preg/treg.has_value() instead of implicit conversion to boolean.
> - used *reg instead of ® for an out parameter.
> - handled language specific type printing using set_language and RAII.
> - no new line after return type for function declaration.
>
> * documentation changes:
> - handled the comments of Eli: rephrase two sentences as one,
> remove redundant blank before :.
> - quoting/backslash handling of TYPEREGEXP slightly updated according
> to the switch to gdb_argv quoting behaviour.
>
>
> Changes between the first RFA and RFAv2:
> ---------------------------------------
> The documentation parts were already reviewed by Eli, other parts
> were not reviewed yet.
> Compared to the first RFA, the changes are a rebase to the last trunk version,
> the removal of an unused local variable, and some updates to the new
> info_qt.exp test to ensure unicity of test names.
>
> Changes between first RFA and the RFC:
> ---------------------------------------
> * Handled comments of Eli on the documentation.
> * ChangeLog entries added in commit messages
> * Test added.
>
> Thanks.
>
>
> This patch series adds flags and/or arguments
> [-q] [-t TYPEREGEXP] [NAMEREGEXP] to the commands
> info [args|functions|locals|variables]
>
> The additional arguments allow to more precisely specify what to print.
> As these new features can usefully be combined with frame apply and thread
> apply, the documentation gives examples combining the above
> and the 'thread apply' and 'frame apply' commands.
>
> Some examples:
> * print functions returning an int:
> info functions -t '^int ('
> * print local variables having pthread_t type
> info locals -t pthread_t
> * print global variables having type 'struct addrinfo'
> info var -t 'struct addrinfo'
> * print args that are likely file descriptors
> info arg -t int .*fd.*
>
> Below examples are combined with the 'thread/frame apply' commands:
>
> * Assuming lock_something_t is an RAII type, show all locks:
> thread apply all -s frame apply all -s info locals -q -t lock_something_t
> or shorter equivalent:
> tfaas i lo -q -t lock_something_t
>
> * show frames and args having an arg with type matchin std::.*map
> so likely std::map or std::unordered_map
> frame apply all -s info args -q std::.*map
>
>
> The code, documentation, NEWS, test and ChangeLog are complete.
>
>
next prev parent reply other threads:[~2018-10-11 19:56 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-23 21:42 Philippe Waroquiers
2018-09-23 21:42 ` [RFAv3 1/5] New cli-utils.h/.c function extract_info_print_args Philippe Waroquiers
2018-10-22 14:16 ` Pedro Alves
2018-10-23 21:59 ` Philippe Waroquiers
2018-10-24 17:03 ` Pedro Alves
2018-09-23 21:42 ` [RFAv3 5/5] Add a test case for info args|functions|locals|variables [-q] [-t TYPEREGEXP] [NAMEREGEXP] Philippe Waroquiers
2018-10-22 14:19 ` Pedro Alves
2018-10-23 22:05 ` Philippe Waroquiers
2018-10-24 17:18 ` Pedro Alves
2018-09-23 21:42 ` [RFAv3 2/5] Add [-q] [-t TYPEREGEXP] [NAMEREGEXP] args to info [args|functions|locals|variables] Philippe Waroquiers
2018-10-22 14:16 ` Pedro Alves
2018-09-23 21:42 ` [RFAv3 4/5] Announce changes in NEWS " Philippe Waroquiers
2018-09-24 6:59 ` Eli Zaretskii
2018-09-23 21:42 ` [RFAv3 3/5] Document changes " Philippe Waroquiers
2018-09-24 7:03 ` Eli Zaretskii
2018-10-22 14:17 ` Pedro Alves
2018-10-02 18:17 ` [RFAv3 0/5] info [args|functions|locals|variables] [-q] [-t TYPEREGEXP] [NAMEREGEXP] Philippe Waroquiers
2018-10-11 19:56 ` Philippe Waroquiers [this message]
2018-10-18 19:37 ` PING^3 " Philippe Waroquiers
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=1539287771.2137.4.camel@skynet.be \
--to=philippe.waroquiers@skynet.be \
--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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).