From: Daniel Jacobowitz <drow@false.org>
To: Luis Machado <luisgpm@linux.vnet.ibm.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] PPC atomic single stepping testcase
Date: Sun, 16 Dec 2007 22:49:00 -0000 [thread overview]
Message-ID: <20071216222531.GA6846@caradoc.them.org> (raw)
In-Reply-To: <1197305093.2060.17.camel@gargoyle>
On Mon, Dec 10, 2007 at 02:44:52PM -0200, Luis Machado wrote:
> * gdb.arch/powerpc64-atomic-single-stepping.c: New testcase source file.
> * gdb.arch/powerpc64-atomic-single-stepping.exp: New testcase expect file.
Is there a shorter name you could give this? :-(
> @@ -0,0 +1,71 @@
> +# Copyright 2006 Free Software Foundation, Inc.
2007.
> +gdb_breakpoint "27" "Breakpoint $decimal at $hex" \
> + "Set the breakpoint at the start of the sequence"
> +
> +gdb_breakpoint "35" "Breakpoint $decimal at $hex" \
> + "Set the breakpoint at the start of the sequence"
Take a look at gdb_get_line_number.
> +gdb_test continue "Continuing.*Breakpoint $decimal.*" \
> + "Continue until breakpoint"
> +
> +gdb_test next "" \
> + "Step through the lwarx/stwcx sequence"
> +
> +gdb_test next "" \
> + "Step through the ldarx/stdcx sequence"
That's not much of a test. I suggest you match enough output
to verify that you ended up where you expected to.
> +gdb_test continue ".*Program exited normally.*" \
> + "Continue until exit"
Is this testing for anything specific? Otherwise, I'd recommend not
doing it; some targets produce different exit messages, et cetera.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2007-12-16 22:25 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-04 20:16 Luis Machado
2007-12-04 23:16 ` Ulrich Weigand
2007-12-05 19:29 ` Luis Machado
2007-12-10 17:31 ` Luis Machado
2007-12-16 22:49 ` Daniel Jacobowitz [this message]
2007-12-18 18:47 ` Luis Machado
2008-01-07 16:10 ` Luis Machado
2008-01-29 17:49 ` Daniel Jacobowitz
2008-01-31 17:25 ` Luis Machado
2007-12-17 4:12 ` Thiago Jung Bauermann
2007-12-04 20:24 Luis Machado
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=20071216222531.GA6846@caradoc.them.org \
--to=drow@false.org \
--cc=gdb-patches@sourceware.org \
--cc=luisgpm@linux.vnet.ibm.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