From: "Frank Ch. Eigler" <fche@redhat.com>
To: Jose Luis Ayala <jayala@die.upm.es>
Cc: cgen@sources.redhat.com
Subject: Re: Memory accesses
Date: Wed, 29 Jan 2003 19:39:00 -0000 [thread overview]
Message-ID: <20030129143917.E22986@redhat.com> (raw)
In-Reply-To: <20030129192238.GA2670@die.upm.es>; from jayala@die.upm.es on Wed, Jan 29, 2003 at 08:22:39PM +0100
[-- Attachment #1: Type: text/plain, Size: 469 bytes --]
Hi -
On Wed, Jan 29, 2003 at 08:22:39PM +0100, Jose Luis Ayala wrote:
> I'm writing some simple code to trace memory accesses while the
> simulator runs. As I want this works for different targets, I need to
> put the code into the common simulator sources. [...]
This is not really a CGEN issue. If you want to deal with either
the gdb simulators or with sid, then chances are the command line
option "--trace-core" will produce tracing output you can use.
- FChE
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
prev parent reply other threads:[~2003-01-29 19:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-29 19:21 Jose Luis Ayala
2003-01-29 19:39 ` Frank Ch. Eigler [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=20030129143917.E22986@redhat.com \
--to=fche@redhat.com \
--cc=cgen@sources.redhat.com \
--cc=jayala@die.upm.es \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).