Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Pedro Alves <palves@redhat.com>
To: Simon Marchi <simon.marchi@ericsson.com>, gdb-patches@sourceware.org
Subject: Re: [PATCH v2] Add mi-threads-interrupt.exp test (PR 20039)
Date: Tue, 17 May 2016 18:35:00 -0000	[thread overview]
Message-ID: <11ba81b6-e28c-0d78-4a23-e1cce17e19b0@redhat.com> (raw)
In-Reply-To: <1462472343-17772-1-git-send-email-simon.marchi@ericsson.com>

On 05/05/2016 07:19 PM, Simon Marchi wrote:
> Add a new test for PR 20039.  The test spawns new threads, then tries to
> interrupt, continue, and interrupt again.  This use case was fixed by
> commit 5fe966540d6b748f825774868463003700f0c878 in master, but gdb 7.11
> is affected (so if you try it on the gdb-7.11-branch right now, the test
> will fail).
> 
> New in v2, the test now handles mi-async on mode properly.  The failure
> was specific to mi-async off, but I don't think it's bad to test the
> same thing under async on mode.  I added a little hack when running in
> async mode to work around bug 20045.
> 
> I also removed one continue/interrupt pair, as a single one was enough to
> trigger the problem.
> 
> gdb/testsuite/ChangeLog:
> 
> 	* gdb.mi/mi-threads-interrupt.c: New file.
> 	* gdb.mi/mi-threads-interrupt.exp: New file.

OK.

Thanks,
Pedro Alves


       reply	other threads:[~2016-05-17 18:35 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1462472343-17772-1-git-send-email-simon.marchi@ericsson.com>
2016-05-17 18:35 ` Pedro Alves [this message]
2016-05-18 13:27 ` Simon Marchi
     [not found]   ` <a4038c0f-cf22-ac47-eccc-a016ce6dbfbe@redhat.com>
2016-05-18 14:22     ` 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=11ba81b6-e28c-0d78-4a23-e1cce17e19b0@redhat.com \
    --to=palves@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --cc=simon.marchi@ericsson.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