From: "Colin Wen" <colinw@aten-ca.com>
To: "Daniel Jacobowitz" <drow@false.org>
Cc: <gdb@sourceware.org>
Subject: Re: View EPC Register on MIPS
Date: Sat, 08 Jul 2006 01:05:00 -0000 [thread overview]
Message-ID: <000401c6a22a$6f834d80$6700000a@colinw01> (raw)
In-Reply-To: <20060707234917.GA4792@nevyn.them.org>
----- Original Message -----
From: "Daniel Jacobowitz" <drow@false.org>
To: "Colin Wen" <colinw@aten-ca.com>
Cc: <gdb@sourceware.org>
Sent: Friday, July 07, 2006 4:49 PM
Subject: Re: View EPC Register on MIPS
> On Fri, Jul 07, 2006 at 04:15:04PM -0700, Colin Wen wrote:
>> Hi,
>>
>> Can anybody please tell me how to view the EPC register on MIPS by gdb?
>> I tried info all-registers but there is no EPC register.
>
> You are probably out of luck. I believe there were a few specific MIPS
> remote debugging stubs that could report EPC, but most can't.
>
> We've been working on extensions that will make it easier to do this
> sort of thing, in future releases.
>
Thanks for your help, then maybe I can try mon comand to directly call
debugger.
colin wen
prev parent reply other threads:[~2006-07-08 1:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-07 23:15 Colin Wen
2006-07-07 23:49 ` Daniel Jacobowitz
2006-07-08 1:05 ` Colin Wen [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='000401c6a22a$6f834d80$6700000a@colinw01' \
--to=colinw@aten-ca.com \
--cc=drow@false.org \
--cc=gdb@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