From: Pedro Alves <pedro@codesourcery.com>
To: gdb-patches@sourceware.org
Subject: Testing gdb/monitor.c
Date: Thu, 03 Jul 2008 14:00:00 -0000 [thread overview]
Message-ID: <200807031459.29209.pedro@codesourcery.com> (raw)
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?
--
Pedro Alves
next reply other threads:[~2008-07-03 14:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-03 14:00 Pedro Alves [this message]
2008-07-03 18:58 ` Michael Snyder
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=200807031459.29209.pedro@codesourcery.com \
--to=pedro@codesourcery.com \
--cc=gdb-patches@sourceware.org \
/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