From: Keith Seitz <keiths@redhat.com>
To: Simon Marchi <simon.marchi@polymtl.ca>,
Tom Tromey <tom@tromey.com>,
Tom de Vries via Gdb-patches <gdb-patches@sourceware.org>
Subject: Re: [PATCH][gdb/testsuite] Support .debug_aranges in dwarf assembly
Date: Fri, 27 Aug 2021 09:11:00 -0700 [thread overview]
Message-ID: <6e2cdfcb-f667-a7ad-b314-0c100a7984ed@redhat.com> (raw)
In-Reply-To: <40b7d95e-cc02-38c7-5406-0fc83a2a1b28@polymtl.ca>
On 8/27/21 8:09 AM, Simon Marchi via Gdb-patches wrote:
>
>
> On 2021-08-27 9:35 a.m., Tom Tromey wrote:
>>>>>>> "Tom" == Tom de Vries via Gdb-patches <gdb-patches@sourceware.org> writes:
>>
>> Tom> + # arange [-c <comment>] [<segment selector>] <start> <length>
>> Tom> + # -- adds an address range.
>>
>> I wonder if there's a way to make this more tcl-ish, say by rearranging
>> the order of arguments so that things can be defaulted. I think the
>> "args"-parsing style should normally be a last resort.
>
> I personally don't like this style
>
> proc arange { arange_start arange_length {comment ""} {seg_sel ""} }
>
> ... because if you want to specify the last parameter, you need to give
> all the other optional ones before.
The test suite also contains the convenience proc parse_args which allows
the use of optional arguments using flag-like syntax and default values.
proc arange {start length args} {
parse_args {{comment ""} {seg_sel ""}}
# ...
}
arange $start $end -comment "a comment"
See the definition in testsuite/lib/gdb.exp for usage examples.
Keith
next prev parent reply other threads:[~2021-08-27 16:11 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-26 11:56 Tom de Vries
2021-08-27 13:35 ` Tom Tromey
2021-08-27 14:39 ` Tom de Vries
2021-08-27 15:09 ` Simon Marchi
2021-08-27 16:11 ` Keith Seitz [this message]
2021-08-27 16:14 ` Tom Tromey
2021-08-27 17:03 ` Simon Marchi
2021-08-27 17:10 ` Tom Tromey
2021-08-27 17:23 ` Simon Marchi
2021-08-28 15:31 ` Tom de Vries
2021-08-28 20:29 ` Simon Marchi
2021-08-28 21:28 ` Simon Marchi
2021-08-29 15:31 ` Tom de Vries
2021-08-29 19:54 ` Simon Marchi
2021-08-29 21:11 ` Tom de Vries
2021-08-30 8:35 ` 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=6e2cdfcb-f667-a7ad-b314-0c100a7984ed@redhat.com \
--to=keiths@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=simon.marchi@polymtl.ca \
--cc=tom@tromey.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).