From: Michael Snyder <msnyder@specifix.com>
To: Pedro Alves <pedro@codesourcery.com>
Cc: gdb-patches@sourceware.org
Subject: Re: Testing gdb/monitor.c
Date: Thu, 03 Jul 2008 18:58:00 -0000 [thread overview]
Message-ID: <1215111474.3549.47.camel@localhost.localdomain> (raw)
In-Reply-To: <200807031459.29209.pedro@codesourcery.com>
On Thu, 2008-07-03 at 14:59 +0100, Pedro Alves wrote:
> Guys,
>
> If I wanted to do some changes to the monitor target(s) (monitor.c),
> what's the best and easiest way to test them? I never used this
> target before. Do I need hardware for that, or is there
> some (maintaned) --target that uses it with a simulator? Or?
Hmmm...
The "monitor" target is for debugging a "bare metal" development
board that has no operating system, and doesn't even have a gdb
"stub" that can communicate using the remote protocol.
It works by sending "rom monitor" type commands and interpreting
their output.
Such a system is unlikely to implement threads.
I understand your desire to canonicalize target thread behavior, though.
I don't know of any way to test the monitor target, except
by using real hardware that has a rom monitor for which gdb
has a syntax spec.
It would certainly be possible to construct a gdbreplay-like
software emulation that would mimic a monitor target, but you
would still need a real one from which to record some sessions.
The return on investment would probably be small, though...
;-/
Michael
next prev parent reply other threads:[~2008-07-03 18:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-03 14:00 Pedro Alves
2008-07-03 18:58 ` Michael Snyder [this message]
2008-07-04 10:58 ` 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=1215111474.3549.47.camel@localhost.localdomain \
--to=msnyder@specifix.com \
--cc=gdb-patches@sourceware.org \
--cc=pedro@codesourcery.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