From: Pedro Alves <palves@redhat.com>
To: Patrick Palka <patrick@parcs.ath.cx>
Cc: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: [PATCH] Fix assert failure in invocation of "[kill|detach] inferiors 1"
Date: Wed, 29 Jul 2015 11:38:00 -0000 [thread overview]
Message-ID: <55B8BB22.40708@redhat.com> (raw)
In-Reply-To: <CA+C-WL9DgzS64K9Jd0wv9gzGyiMP-GwJ-RVt2z-h2DsSw6rMag@mail.gmail.com>
On 07/29/2015 12:22 PM, Patrick Palka wrote:
> Ah, so the internal error may also be triggered by passing to these
> commands an inferior that is not being run, not just by passing the
> initial dummy inferior. I will change the test file to cover these
> bases.
Yeah. The initial inferior is no different from any other inferior
that is created afterwards.
> I notice that "[kill|attach] inferiors" has no test coverage
> at all, so this will be a good time to add some.
Thanks, that's super.
--
Pedro Alves
prev parent reply other threads:[~2015-07-29 11:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-28 20:30 Patrick Palka
2015-07-28 23:42 ` Pedro Alves
2015-07-29 11:23 ` Patrick Palka
2015-07-29 11:38 ` Pedro Alves [this message]
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=55B8BB22.40708@redhat.com \
--to=palves@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=patrick@parcs.ath.cx \
/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