From: Elena Zannoni <ezannoni@redhat.com>
To: Kevin Buettner <kevinb@redhat.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFC] gdb.base/args.exp: Invoke gdb_load for simulator targets
Date: Tue, 08 Apr 2003 22:44:00 -0000 [thread overview]
Message-ID: <16019.20933.407808.340358@localhost.redhat.com> (raw)
In-Reply-To: <1030408222709.ZM13182@localhost.localdomain>
Kevin Buettner writes:
> I'm testing gdb against a simulator and I'm seeing the following in
> the gdb.log output:
>
> (gdb) run
> Starting program: .../gdb/testsuite/gdb.base/args 1 3
> Don't know how to run. Try "help target".
> (gdb) FAIL: gdb.base/args.exp: correct args printed
>
> My first inclination was to simply skip this test for simulator
> targets, but I decided that there's no reason not to run it. I've
> added a bit of code to invoke gdb_load for simulator targets and
> wrapped it up in a proc so that it'll be easier to augment as other
> targets are identified which can use a similar mechanism.
>
> Comments? (This is reasonably obvious, so I'll check this in a day or
> so if there are no objections.)
>
Ah, thanks for fixing this Kevin. I remembered now that Michael Snyder
complained about the same problem, and I forgot to go back and fix it.
elena
> * gdb.base/args.exp: Invoke gdb_load for simulator targets.
> Modify regexps to match extra output after program exit in a
> simulator.
>
> Index: gdb.base/args.exp
> ===================================================================
> RCS file: /cvs/cvsfiles/devo/gdb/testsuite/gdb.base/args.exp,v
> retrieving revision 1.3
> diff -u -p -r1.3 args.exp
> --- args.exp 2003/03/27 22:01:24 1.3
> +++ args.exp 2003/04/08 22:04:40
> @@ -31,6 +31,15 @@ if [target_info exists noargs] {
> return;
> }
>
> +# No loading needs to be done when the target is `exec'. Some targets
> +# require that the program be loaded, however.
> +proc args_load {} {
> + global binfile
> + if [target_info exists is_simulator] {
> + gdb_load ${binfile}
> + }
> +}
> +
> set testfile "args"
> set srcfile ${testfile}.c
> set binfile ${objdir}/${subdir}/${testfile}
> @@ -47,8 +56,9 @@ set GDBFLAGS "--args $binfile 1 3"
> gdb_exit
> gdb_start
> gdb_reinitialize_dir $srcdir/$subdir
> +args_load
> gdb_test "run" \
> - "Starting program.*args(\\.exe)? 1 3.*3\r\n.*args\r\n1\r\n3.*Program exited normally." \
> + "Starting program.*args(\\.exe)? 1 3.*3\r\n.*args\r\n1\r\n3.*Program exited normally.*" \
> "correct args printed"
>
> #
> @@ -58,8 +68,9 @@ set GDBFLAGS "--args $binfile 1 '' 3"
> gdb_exit
> gdb_start
> gdb_reinitialize_dir $srcdir/$subdir
> +args_load
> gdb_test "run" \
> - "Starting program.*args(\\.exe)? 1 \\\\'\\\\' 3.*4\r\n.*args\r\n1\r\n''\r\n3.*Program exited normally." \
> + "Starting program.*args(\\.exe)? 1 \\\\'\\\\' 3.*4\r\n.*args\r\n1\r\n''\r\n3.*Program exited normally.*" \
> "correct args printed, one empty"
>
> #
> @@ -69,8 +80,9 @@ set GDBFLAGS "--args $binfile 1 '' '' 3"
> gdb_exit
> gdb_start
> gdb_reinitialize_dir $srcdir/$subdir
> +args_load
> gdb_test "run" \
> - "Starting program.*args(\\.exe)? 1 \\\\'\\\\' \\\\'\\\\' 3.*5\r\n.*args\r\n1\r\n''\r\n''\r\n3.*Program exited normally." \
> + "Starting program.*args(\\.exe)? 1 \\\\'\\\\' \\\\'\\\\' 3.*5\r\n.*args\r\n1\r\n''\r\n''\r\n3.*Program exited normally.*" \
> "correct args printed, two empty"
>
> set GDBFLAGS $old_gdbflags
next prev parent reply other threads:[~2003-04-08 22:44 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-08 22:27 Kevin Buettner
2003-04-08 22:44 ` Elena Zannoni [this message]
2003-04-09 14:21 ` Andrew Cagney
2003-04-09 16:07 ` Kevin Buettner
2003-04-09 16:15 ` Andrew Cagney
2003-04-13 19:46 ` Michael Snyder
2003-04-15 1:41 ` Elena Zannoni
2003-04-16 20:32 ` Kevin Buettner
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=16019.20933.407808.340358@localhost.redhat.com \
--to=ezannoni@redhat.com \
--cc=gdb-patches@sources.redhat.com \
--cc=kevinb@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