From: Joel Brobecker <brobecker@adacore.com>
To: Pedro Alves <palves@redhat.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: Mon, 15 Sep 2014 13:55:00 -0000 [thread overview]
Message-ID: <20140915135527.GK4871@adacore.com> (raw)
In-Reply-To: <54136947.4020003@redhat.com>
> OOC, how does one debug Ravenscar then? Does that sit on top of
> target remote ?
The ravenscar target is more like a "thread" target, and depends on
the runtime being used. So, it can sit on top of any execution target,
remote, native, etc. To be able to test it, you need an Ada compiler
with a ravenscar runtime. Not sure if the GCC from FSF has those
runtimes out of the box, but we provide an arm-eabi GNAT toolchain
on libre.adacore.com, if you ever need it.
--
Joel
prev parent reply other threads:[~2014-09-15 13:55 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
2014-09-12 22:45 ` Pedro Alves
2014-09-15 13:55 ` Joel Brobecker [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=20140915135527.GK4871@adacore.com \
--to=brobecker@adacore.com \
--cc=emachado@linux.vnet.ibm.com \
--cc=gdb-patches@sourceware.org \
--cc=palves@redhat.com \
--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