From: Michael Snyder <Michael.Snyder@palmsource.com>
To: Cai Qian <caiqian@gmail.com>
Cc: Neo <cjia@cse.unl.edu>, gdb@sourceware.org
Subject: Re: Virtual Machine and GDB
Date: Mon, 21 Aug 2006 19:16:00 -0000 [thread overview]
Message-ID: <1156187793.9010.9.camel@localhost.localdomain> (raw)
In-Reply-To: <a96350810608211157p57edbcc3s2df5213ec78efff8@mail.gmail.com>
On Mon, 2006-08-21 at 19:57 +0100, Cai Qian wrote:
> OK. The VM does not have a debugger at the moment. That is why I try
> to debug remotely. "New instruction set" means it is not i386, SPARC,
> SuperH etc, and GDB does not support the arch yet.
Right -- so once you get your gdbserver to talk to gdb,
the next thing you have to do is teach gdb to understand
your new architecture.
If you look at some of the base architecture ports that you
mentioned, for instance sh-tdep.c or h8300-tdep.c, these
are examples of what I mean. They tell gdb how to interpret
the register set etc. of the given target architecture.
You need to write one of these for your target.
next prev parent reply other threads:[~2006-08-21 19:16 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-20 21:10 Cai Qian
2006-08-21 0:07 ` Daniel Jacobowitz
2006-08-21 0:24 ` Cai Qian
2006-08-21 1:54 ` Daniel Jacobowitz
[not found] ` <daef60380608201849o49825a32s135b8131807ee71f@mail.gmail.com>
2006-08-21 10:25 ` Cai Qian
2006-08-21 11:38 ` teawater
2006-08-21 12:22 ` Cai Qian
2006-08-21 12:48 ` Daniel Jacobowitz
2006-08-21 13:35 ` teawater
2006-08-21 17:04 ` Neo
2006-08-21 17:59 ` Cai Qian
2006-08-21 18:28 ` Michael Snyder
2006-08-21 18:32 ` Daniel Jacobowitz
2006-08-21 18:50 ` Cai Qian
2006-08-21 19:13 ` Michael Snyder
2006-08-21 18:30 ` Neo
2006-08-21 18:57 ` Cai Qian
2006-08-21 19:16 ` Michael Snyder [this message]
2006-08-22 1:21 ` teawater
2006-08-22 6:26 Anupama Chandwani
2006-08-22 6:26 Anupama Chandwani
2006-08-22 6:26 Anupama Chandwani
2006-08-22 6:26 Anupama Chandwani
2006-08-22 6:26 Anupama Chandwani
2006-08-22 6:26 Anupama Chandwani
2006-08-22 6:26 Anupama Chandwani
2006-08-22 6:26 Anupama Chandwani
2006-08-22 6:26 Anupama Chandwani
2006-08-22 6:26 Anupama Chandwani
2006-08-22 6:26 Anupama Chandwani
2006-08-22 6:26 Anupama Chandwani
2006-08-22 6:26 Anupama Chandwani
2006-08-22 6:26 Anupama Chandwani
2006-08-22 6:26 Anupama Chandwani
2006-08-22 6:26 Anupama Chandwani
2006-08-22 6:26 Anupama Chandwani
2006-08-22 6:26 Anupama Chandwani
2006-08-22 6:26 Anupama Chandwani
2006-08-22 6:26 Anupama Chandwani
2006-08-22 6:26 Anupama Chandwani
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=1156187793.9010.9.camel@localhost.localdomain \
--to=michael.snyder@palmsource.com \
--cc=caiqian@gmail.com \
--cc=cjia@cse.unl.edu \
--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