From: Pedro Alves <pedro@palves.net>
To: Simon Marchi <simark@simark.ca>, gdb-patches@sourceware.org
Subject: Re: [RESEND][PATCH 5/5] Eliminate mi_run_to_main, introduce mi_clean_restart
Date: Tue, 13 Oct 2020 22:36:44 +0100 [thread overview]
Message-ID: <6d6a7ad8-c6fe-4e35-d27c-bc165bcf9c82@palves.net> (raw)
In-Reply-To: <0e501a33-cd2a-d680-a1b4-a76a45d8cea1@simark.ca>
On 10/13/20 7:19 PM, Simon Marchi wrote:
> On 2020-10-12 2:56 p.m., Pedro Alves wrote:
>> diff --git a/gdb/testsuite/lib/mi-support.exp b/gdb/testsuite/lib/mi-support.exp
>> index 693c7d2c467..0de3aa8703a 100644
>> --- a/gdb/testsuite/lib/mi-support.exp
>> +++ b/gdb/testsuite/lib/mi-support.exp
>> @@ -1023,28 +1023,41 @@ proc mi_run_with_cli {args} {
>> return [eval mi_run_cmd_full 0 $args]
>> }
>>
>> -#
>> -# Just like run-to-main but works with the MI interface
>> -#
>> -
>> -proc mi_run_to_main { } {
>> - global suppress_flag
>> - if { $suppress_flag } {
>> - return -1
>> - }
>> +# Starts fresh GDB binary and loads an optional executable into GDB.
>> +# Usage: mi_clean_restart [executable]
>> +# EXECUTABLE is the basename of the binary.
>> +# Return -1 if starting gdb or loading the executable failed.
>>
>> +proc mi_clean_restart { args } {
>
> Again, for a new optional argument I'd suggest using parse_args,
> meaning calling mi_clean_restart with an explicit binfile would be:
>
> mi_clean_restart -binfile ${binfile}
>
> But, this is not very important, the next person to add an argument to
> mi_clean_restart can do it (if it ever happens). The patch LGTM as it
> is.
Yeah, I left this one as is to have it mirror the CLI's clean_restart.
Thanks for the quick reviews. I've merged the series now.
Pedro Alves
next prev parent reply other threads:[~2020-10-13 21:36 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-12 0:47 [PATCH 0/5] runto_main and -qualified Pedro Alves
2020-10-12 0:47 ` [PATCH 1/5] 'runto main' -> 'runto_main' throughout Pedro Alves
2020-10-13 17:57 ` Simon Marchi
2020-10-12 0:47 ` [PATCH 2/5] Introduce mi_runto_main Pedro Alves
2020-10-13 18:00 ` Simon Marchi
2020-10-12 0:47 ` [PATCH 3/5] gdb/testsuite/: Use -qualified in runto_main / mi_runto_main Pedro Alves
2020-10-13 18:06 ` Simon Marchi
2020-10-13 21:33 ` Pedro Alves
2020-10-12 0:47 ` [PATCH 4/5] gdb/testsuite/: Use "-qualified" in explicit "break main", etc Pedro Alves
2020-10-13 18:07 ` Simon Marchi
2020-10-12 18:56 ` [RESEND][PATCH 5/5] Eliminate mi_run_to_main, introduce mi_clean_restart Pedro Alves
2020-10-13 18:19 ` Simon Marchi
2020-10-13 21:36 ` Pedro Alves [this message]
2020-10-14 8:40 ` 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=6d6a7ad8-c6fe-4e35-d27c-bc165bcf9c82@palves.net \
--to=pedro@palves.net \
--cc=gdb-patches@sourceware.org \
--cc=simark@simark.ca \
/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