Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Hui Zhu <hui_zhu@mentor.com>
To: Pedro Alves <palves@redhat.com>
Cc: gdb-patches ml <gdb-patches@sourceware.org>
Subject: Re: [PATCH 1/1] Fix internal warning when "gdb -p xxx" (test)
Date: Fri, 21 Mar 2014 03:27:00 -0000	[thread overview]
Message-ID: <532BB1AD.8010200@mentor.com> (raw)
In-Reply-To: <532ACB1B.2090207@redhat.com>

On 03/20/14 19:03, Pedro Alves wrote:
> On 03/20/2014 03:16 AM, Hui Zhu wrote:
>
>> +    expect {
>> +	-re "Reading symbols from.*$gdb_prompt $" {
>> +            pass "$test"
>> +	}
>> +	timeout {
>> +	    fail "$test (timeout)"
>
> Something odd with indentation here.

Change 8 blank to a tab.

>
> Otherwise OK.  Please push.
>
> Thanks,
>

Thanks for your help.

Committed to
https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=ccdd1909ad5299cf0753aaa113928a41f8f27391

Best,
Hui


      reply	other threads:[~2014-03-21  3:27 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-17 16:00 [PATCH 0/1] Fix internal warning when "gdb -p xxx" Hui Zhu
2014-03-17 16:02 ` [PATCH 1/1] Fix memleak of the pid_to_exec_file target_ops method for some platforms Hui Zhu
2014-03-18  7:39   ` Hui Zhu
2014-03-17 16:12 ` [PATCH 0/1] Fix internal warning when "gdb -p xxx" Pedro Alves
2014-03-17 16:57   ` Pedro Alves
2014-03-18  7:38     ` Hui Zhu
2014-03-18 10:14       ` Pedro Alves
2014-03-19  3:58         ` Hui Zhu
2014-03-19 10:16           ` Pedro Alves
2014-03-20  2:58             ` Hui Zhu
2014-03-20  3:27               ` Hui Zhu
2014-03-20 12:56                 ` Pedro Alves
2014-03-21  3:14                   ` Hui Zhu
2014-03-19  4:03         ` [PATCH 1/1] Fix internal warning when "gdb -p xxx" (test) Hui Zhu
2014-03-19 10:28           ` Pedro Alves
2014-03-20  3:16             ` Hui Zhu
2014-03-20 12:23               ` Pedro Alves
2014-03-21  3:27                 ` Hui Zhu [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=532BB1AD.8010200@mentor.com \
    --to=hui_zhu@mentor.com \
    --cc=gdb-patches@sourceware.org \
    --cc=palves@redhat.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