Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Will Newton <will.newton@linaro.org>
To: Tom Tromey <tromey@redhat.com>
Cc: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>,
	Patch Tracking <patches@linaro.org>
Subject: Re: [PATCH 3/3] gdb/testsuite/gdb.cp/annota2.exp: Add missing empty line, in output.
Date: Wed, 05 Jun 2013 17:48:00 -0000	[thread overview]
Message-ID: <CANu=DmgWvi_aAaf9MH4mT7Z=NusJ=t4Yj2rVSkTwyQwbxaZaeQ@mail.gmail.com> (raw)
In-Reply-To: <87r4ggk17a.fsf@fleche.redhat.com>

On 5 June 2013 16:48, Tom Tromey <tromey@redhat.com> wrote:
>>>>>> "Will" == Will Newton <will.newton@linaro.org> writes:
>
> Will> There should be an empty line between "post-prompt" and "starting".
> Will> This fixes a testsuite failure on ARM.
>
> Will> gdb/testsuite/ChangeLog:
>
> Will> 2013-06-05  Will Newton  <will.newton@linaro.org>
>
> Will>   * gdb.cp/annota2.exp: Add empty line between "post-prompt"
> Will>   and "starting".
>
> This is ok.
>
> This test still KFAILs for me, on x86-64 F18.
> It seems that the watchpoint doesn't actually trigger.

I get a KFAIL on x86_64 also, but on ARM prior to this change I would
get a timeout.

I can commit to binutils but not have not committed to gdb thus far.

--
Will Newton
Toolchain Working Group, Linaro


  reply	other threads:[~2013-06-05 17:48 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-05 10:34 Will Newton
2013-06-05 15:49 ` Tom Tromey
2013-06-05 17:48   ` Will Newton [this message]
2013-06-05 19:19     ` Tom Tromey
2013-06-06  9:04       ` Will Newton
2013-06-06 10:33         ` 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='CANu=DmgWvi_aAaf9MH4mT7Z=NusJ=t4Yj2rVSkTwyQwbxaZaeQ@mail.gmail.com' \
    --to=will.newton@linaro.org \
    --cc=gdb-patches@sourceware.org \
    --cc=patches@linaro.org \
    --cc=tromey@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