Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Pedro Alves <pedro@palves.net>
To: Simon Marchi <simark@simark.ca>, gdb-patches@sourceware.org
Subject: Re: [PATCH 1/2] Split gdb.multi/multi-target.exp into separate testcases
Date: Fri, 18 Sep 2020 13:34:49 +0100	[thread overview]
Message-ID: <443e031f-68bc-a4cb-61ae-e63a6c6c1638@palves.net> (raw)
In-Reply-To: <f5746190-91b2-606e-7502-6055e5c9486d@simark.ca>

On 9/17/20 8:16 PM, Simon Marchi wrote:
> On 2020-09-17 2:00 p.m., Pedro Alves wrote:
>> gdb.multi/multi-target.exp sets up a debug environment with multiple
>> gdbservers, multiple native processes, and multiple cores, which has
>> proved useful for exercising a number of multi-target scenarios.
>>
>> But, as we add more tests to gdb.base/multi-target.exp, it is growing
>> a bit too large (making a bit cumbersome to debug) and too slow to run
>> (if you have glibc debug info).
>>
>> This commit thus splits the multi-target.exp into several testcases,
>> one per use case.  The common setup code is moved to a new
>> multi-target.exp.tcl file that is included by all the resulting
>> multi-target testcases.
> 
> Nice, that makes the test cases much more readable too.

I agree.

>> +    # We're use inferiors 1 and 2.  Make sure they're really connected
> 
> I just spotted this typo: "use" -> "using".

I think I originally meant to say "We'll use".  I fixed it to use that.


  reply	other threads:[~2020-09-18 12:34 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-17 18:00 [PATCH 0/2] Fix "thread find" with multi inferior/target (PR gdb/26631) Pedro Alves
2020-09-17 18:00 ` [PATCH 1/2] Split gdb.multi/multi-target.exp into separate testcases Pedro Alves
2020-09-17 19:16   ` Simon Marchi
2020-09-18 12:34     ` Pedro Alves [this message]
2020-09-17 19:41   ` Simon Marchi
2020-09-18 13:01     ` Pedro Alves
2020-09-17 18:00 ` [PATCH 2/2] Fix "thread find" with multiple inferiors/targets (PR gdb/26631) Pedro Alves
2020-09-17 19:37   ` Simon Marchi

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=443e031f-68bc-a4cb-61ae-e63a6c6c1638@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