Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Pedro Alves <palves@redhat.com>
To: Yao Qi <qiyaoltc@gmail.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] Fix PR threads/19422 - show which thread caused stop
Date: Mon, 18 Jan 2016 15:24:00 -0000	[thread overview]
Message-ID: <569D039F.3080404@redhat.com> (raw)
In-Reply-To: <86si20tael.fsf@gmail.com>

On 01/14/2016 04:04 PM, Yao Qi wrote:

>> gdb/testsuite/ChangeLog:
>> 2016-01-04  Pedro Alves  <palves@redhat.com>
>>
>> 	* gdb.base/async-shell.exp: Adjust expected output.
>> 	* gdb.base/dprintf-non-stop.exp: Adjust expected output.
>> 	* gdb.base/siginfo-thread.exp
>> 	* gdb.base/watchpoint-hw-hit-once.exp
>> 	* gdb.java/jnpe.exp
>> 	* gdb.threads/clone-new-thread-event.exp
>> 	* gdb.threads/continue-pending-status.exp
>> 	* gdb.threads/leader-exit.exp
>> 	* gdb.threads/manythreads.exp
>> 	* gdb.threads/pthreads.exp
>> 	* gdb.threads/schedlock.exp
>> 	* gdb.threads/siginfo-threads.exp
>> 	* gdb.threads/signal-command-multiple-signals-pending.exp
>> 	* gdb.threads/signal-delivered-right-thread.exp
>> 	* gdb.threads/sigthread.exp
>> 	* gdb.threads/watchpoint-fork.exp
> 

> "Likewise" is missing for these changed files in ChangeLog.  Patch looks
> good to me.

Thanks Yao.  (I had fixed that in v2.)

The patch is now pushed.

Given that this only affects the CLI, I think we're free to
tweak it further if people find issues as they start using it,
without worry of breaking scripts/frontends.

Thanks,
Pedro Alves


      reply	other threads:[~2016-01-18 15:24 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-04 23:30 Pedro Alves
2016-01-14 14:08 ` [PATCH+doc] " Pedro Alves
2016-01-14 16:36   ` Eli Zaretskii
2016-01-14 17:12     ` Pedro Alves
2016-01-14 18:25       ` Eli Zaretskii
2016-01-14 19:00         ` Pedro Alves
2016-01-14 19:06           ` Eli Zaretskii
2016-01-18 15:17             ` Pedro Alves
2016-01-22 16:44   ` Jan Kratochvil
2016-01-22 16:55     ` Pedro Alves
2016-01-22 16:56       ` Jan Kratochvil
2016-01-22 17:30   ` [testsuite patch] Fix PR threads/19422 regression + Guile regression [Re: [PATCH+doc] Fix PR threads/19422 - show which thread caused stop] Jan Kratochvil
2016-01-22 17:31     ` [testsuite patch]#2 " Jan Kratochvil
2016-01-22 18:18       ` [testsuite patch]#3 " Jan Kratochvil
2016-01-22 18:37       ` [testsuite patch]#2 " Pedro Alves
2016-01-22 20:05         ` Jan Kratochvil
2016-01-22 20:11           ` Pedro Alves
2016-01-22 20:17             ` Pedro Alves
2016-01-22 20:25               ` [commit] " Jan Kratochvil
2016-01-22 20:44                 ` Pedro Alves
2016-01-22 20:51                   ` [commit#2] " Jan Kratochvil
2016-01-22 20:53                     ` Pedro Alves
2016-01-14 16:04 ` [PATCH] Fix PR threads/19422 - show which thread caused stop Yao Qi
2016-01-18 15:24   ` 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=569D039F.3080404@redhat.com \
    --to=palves@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --cc=qiyaoltc@gmail.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