From: Daniel Jacobowitz <dan@debian.org>
To: Gareth <g.c.bransby-99@student.lboro.ac.uk>
Cc: linux-mips@linux-mips.org
Subject: Re: Instruction tracing
Date: Fri, 13 Sep 2002 10:18:40 -0400 [thread overview]
Message-ID: <20020913141840.GA12165@nevyn.them.org> (raw)
In-Reply-To: <20020913151236.45429b74.g.c.bransby-99@student.lboro.ac.uk>
On Fri, Sep 13, 2002 at 03:12:36PM +0100, Gareth wrote:
> Hello,
>
> I am trying to debug a program running on a mips malta dev board (no operating
> system). I am using gdb running on a linux pc connected to the board via
> serial and the board is running YAMON gdb. I can step through the code, set
> break points, examine memory and variables etc, but what I would really like
> to do is get an instruction trace of the program.
>
> Any help greatly appreciated.
Sorry, but I don't believe GDB supports this. Some simulators or
probes may support it directly but core GDB really can't do anything
about it.
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
prev parent reply other threads:[~2002-09-13 14:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-13 14:12 Instruction tracing Gareth
2002-09-13 14:18 ` Daniel Jacobowitz [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=20020913141840.GA12165@nevyn.them.org \
--to=dan@debian.org \
--cc=g.c.bransby-99@student.lboro.ac.uk \
--cc=linux-mips@linux-mips.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