public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "anton.kochkov at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/12602] New: Support of coprocessor registers: cp14, cp15, etc
Date: Wed, 23 Mar 2011 16:43:00 -0000	[thread overview]
Message-ID: <bug-12602-4717@http.sourceware.org/bugzilla/> (raw)


http://sourceware.org/bugzilla/show_bug.cgi?id=12602

           Summary: Support of coprocessor registers: cp14, cp15, etc
           Product: gdb
           Version: unknown
            Status: NEW
          Severity: enhancement
          Priority: P2
         Component: gdb
        AssignedTo: unassigned@sourceware.org
        ReportedBy: anton.kochkov@gmail.com


On modern ARM processors always included coprocessor logic (usually called
cp14, cp15, etc)
Each coprocessor have its own register set.

Please, add support of printing/writing somehow these registers.
So this need to be supported in the server and in the remote client

I'm already using qemu with embedded gdb server (qemu have support of
coprocessor logic)

Also I'm found this project http://jtagarmgdbsrvr.sourceforge.net/index.html
which have initial support of cp15 registers set

-- 
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.


             reply	other threads:[~2011-03-23 16:43 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-23 16:43 anton.kochkov at gmail dot com [this message]
2011-03-23 16:47 ` [Bug gdb/12602] " anton.kochkov at gmail dot com
2011-03-23 17:14 ` anton.kochkov at gmail dot com
2011-03-23 17:44 ` 400757 at gmail dot com
2011-03-23 17:58 ` mfricke at gmail dot com
2022-04-08  1:37 ` [Bug tdep/12602] " tromey at sourceware dot org

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=bug-12602-4717@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=gdb-prs@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).