public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Pedro Alves <palves@redhat.com>
To: Andrew Burgess <andrew.burgess@embecosm.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH 1/3] gdb/testsuite: Fix broken regexp in gdbstub case
Date: Fri, 04 May 2018 09:18:00 -0000	[thread overview]
Message-ID: <193a7d7f-ab07-a8f2-51f7-34cb4ae35a93@redhat.com> (raw)
In-Reply-To: <20180503194115.GJ3375@embecosm.com>

On 05/03/2018 08:41 PM, Andrew Burgess wrote:
> * Pedro Alves <palves@redhat.com> [2018-04-13 13:12:30 +0100]:
> 
>> On 04/09/2018 04:15 PM, Andrew Burgess wrote:
>>> When $use_gdb_stub is true then, when we start an MI target there's a
>>> regexp to match GDB's startup pattern.  Unfortunately the pattern is
>>> broken, and we're also missing a timeout case in the match list (which
>>> would have helped point out that the regexp was broken).
>>
>> That seems to have been added by:
>>  https://sourceware.org/ml/gdb-patches/2015-12/msg00357.html
>>
>> curious how it seems to have worked back then.  I wonder whether
>> it was GDB's CLI-in-MI output that changed meanwhile?
>>
>> I'd have appreciated a bit more detail on what is actually broken in
>> the pattern.  The git log above gives no clue, and the diff is not
>> exactly easy to read.  I trust that it's now correct though.  Thus, OK.
> 
> I aim to please, 

:-)

> so here's a revised commit message detailing what
> changed.  The actual patch content hasn't changed.  I'll wait a few
> days, but if I don't hear anything I'll assume your approval above
> still stands and apply the patch.

Perfect.  This is OK.

Thanks,
Pedro Alves

  reply	other threads:[~2018-05-04  9:18 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-09 15:15 [PATCH 0/3] Small testsuite updates Andrew Burgess
2018-04-09 15:15 ` [PATCH 3/3] gdb/testsuite: Handle targets with lots of registers Andrew Burgess
2018-04-12 23:40   ` Maciej W. Rozycki
2018-04-13 13:10     ` Pedro Alves
2018-04-13 13:57       ` Maciej W. Rozycki
2018-05-04 12:01         ` Andrew Burgess
2018-05-04 12:47           ` Pedro Alves
2018-04-09 15:15 ` [PATCH 1/3] gdb/testsuite: Fix broken regexp in gdbstub case Andrew Burgess
2018-04-13 12:12   ` Pedro Alves
2018-05-03 19:41     ` Andrew Burgess
2018-05-04  9:18       ` Pedro Alves [this message]
2018-04-09 15:15 ` [PATCH 2/3] gdb/testsuite: Filter out some registers for riscv Andrew Burgess
2018-04-09 21:28   ` Palmer Dabbelt
2018-04-09 22:26     ` Andrew Burgess
2018-04-10 20:25       ` Palmer Dabbelt
2018-04-13 12:55         ` Pedro Alves

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=193a7d7f-ab07-a8f2-51f7-34cb4ae35a93@redhat.com \
    --to=palves@redhat.com \
    --cc=andrew.burgess@embecosm.com \
    --cc=gdb-patches@sourceware.org \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).