public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: Martin Simmons <qqxnjvamvxwx@dyxyl.com>
To: "S. Champailler" <schampailler@skynet.be>
Cc: gdb@sourceware.org
Subject: Re: 6502  support in GDB
Date: Fri, 07 Jan 2022 16:53:30 +0000	[thread overview]
Message-ID: <jefspzjxmd.fsf@dyxyl.com> (raw)
In-Reply-To: <34b35bd0.606c.17e33e5b812.Webtop.188@skynet.be> (gdb@sourceware.org)

>>>>> On Fri, 7 Jan 2022 10:36:39 +0100 (CET), S Champailler via Gdb said:
> 
> I was wondering if it is "easy" to add support for a CPU in GDB. 
> Specifically the 6502.

Someone claims to have done this for the m6809 in GDB 7.6 so maybe that
will give some ideas:

https://www.6809.org.uk/dragon/m6809-gdb.shtml

__Martin

      parent reply	other threads:[~2022-01-07 16:53 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-07  9:36 S. Champailler
2022-01-07 10:43 ` Andrew Burgess
2022-01-07 10:58 ` S. Champailler
2022-01-07 16:53 ` Martin Simmons [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=jefspzjxmd.fsf@dyxyl.com \
    --to=qqxnjvamvxwx@dyxyl.com \
    --cc=gdb@sourceware.org \
    --cc=schampailler@skynet.be \
    /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).