From: Pedro Alves <palves@redhat.com>
To: Joel Brobecker <brobecker@adacore.com>
Cc: Edjunior Barbosa Machado <emachado@linux.vnet.ibm.com>,
gdb-patches@sourceware.org,
Ulrich Weigand <uweigand@de.ibm.com>,
Sergio Durigan Junior <sergiodj@redhat.com>
Subject: Re: [PATCH] after gdb_run_cmd, gdb_expect -> gdb_test_multiple/gdb_test
Date: Fri, 12 Sep 2014 21:44:00 -0000 [thread overview]
Message-ID: <54136947.4020003@redhat.com> (raw)
In-Reply-To: <20140912171051.GF4871@adacore.com>
On 09/12/2014 06:10 PM, Joel Brobecker wrote:
>>> I'm writing a test that converts all gdb_run_cmd -> gdb_expect
>>> cases to avoid this from spreading further.
>>
>> Patch pasted below.
>
> Thanks Pedro. I started reviewing it, and then switch to scanner-mode
> half way through. It looks great!
Thanks Joel. Now pushed.
>> In a2-run.exp I converted one vxworks path, but left the others
>> in place... I'm tempted to nuke most of that vxworks stuff
>> out of the testsuite. Does anyone still care about it?
>
> I suspect no one does. I even suspect that no one even cares
> about whatever old version of vxworks is supported by GDB.
> IIRC, that code pre-dates my involvement in the GDB project,
> which started around 2001.
Oh, I notice that the vxworks support the testsuite is caring
about must be for a "target vxworks_or_something", not
"target remote", because we have in
gdb/testsuite/gdb.base/default.exp:
} elseif [istarget "*-*-vxworks*"] then {
gdb_test "set args" ".*" ""
gdb_test "r" "Starting program: .*
You must specify a function name to run, and arguments if any"\
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
"run \"r\" abbreviation"
gdb_test "set args main" ".*" ""
And indeed, that target has been removed 10 years ago already ...
commit e84ecc995d6a5e4e9114d3cea61717b8a573afb6
Author: Andrew Cagney <cagney@redhat.com>
AuthorDate: Sat Nov 13 23:10:02 2004 +0000
2004-11-13 Andrew Cagney <cagney@gnu.org>
* configure.tgt: Delete i[34567]86-*-vxworks*, m68*-netx-*,
m68*-*-vxworks*, mips*-*-vxworks*, powerpc-*-vxworks*, and
sparc-*-vxworks*.
* NEWS: Mention that vxworks was deleted.
Which had:
-static void
-vx_create_inferior (char *exec_file, char *args, char **env, int from_tty)
-{
- enum clnt_stat status;
- arg_array passArgs;
- TASK_START taskStart;
-
- memset ((char *) &passArgs, '\0', sizeof (passArgs));
- memset ((char *) &taskStart, '\0', sizeof (taskStart));
-
- /* parse arguments, put them in passArgs */
-
- parse_args (args, &passArgs);
-
- if (passArgs.arg_array_len == 0)
- error ("You must specify a function name to run, and arguments if any");
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
So I'm going to delete all that cruft.
OOC, how does one debug Ravenscar then? Does that sit on top of
target remote ?
Thanks,
Pedro Alves
next prev parent reply other threads:[~2014-09-12 21:44 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-11 23:03 [PATCH] [PR tdep/17379] Fix internal-error when stack pointer is invalid Edjunior Barbosa Machado
2014-09-11 23:21 ` Sergio Durigan Junior
2014-09-12 2:47 ` Edjunior Barbosa Machado
2014-09-12 3:20 ` Sergio Durigan Junior
2014-09-12 8:39 ` Ulrich Weigand
2014-09-12 9:59 ` Pedro Alves
2014-09-12 12:31 ` Edjunior Barbosa Machado
2014-09-12 13:00 ` Joel Brobecker
2014-09-12 13:38 ` Pedro Alves
2014-09-12 13:50 ` Joel Brobecker
2014-09-12 14:21 ` Pedro Alves
2014-09-12 15:27 ` [PATCH] after gdb_run_cmd, gdb_expect -> gdb_test_multiple/gdb_test Pedro Alves
2014-09-12 17:10 ` Joel Brobecker
2014-09-12 21:44 ` Pedro Alves [this message]
2014-09-12 22:45 ` Pedro Alves
2014-09-15 13:55 ` Joel Brobecker
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=54136947.4020003@redhat.com \
--to=palves@redhat.com \
--cc=brobecker@adacore.com \
--cc=emachado@linux.vnet.ibm.com \
--cc=gdb-patches@sourceware.org \
--cc=sergiodj@redhat.com \
--cc=uweigand@de.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