Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: teawater <teawater@gmail.com>
To: "Cai Qian" <caiqian@gmail.com>
Cc: gdb@sourceware.org
Subject: Re: Virtual Machine and GDB
Date: Mon, 21 Aug 2006 13:35:00 -0000	[thread overview]
Message-ID: <daef60380608210634q7085cda2p3faeef2a517fd9af@mail.gmail.com> (raw)
In-Reply-To: <a96350810608210522l28f7aa68y8eb9167233a19f5d@mail.gmail.com>

Sorry, I told about ARCH because I think you were the people that ask
the same question in CLF.
He told that his VM has a new instruction set. So I think the ARCH of
his VM is not support by GDB.
If the ARCH of your VM is supported by GDB, you will not need to porting it.

>>2) Can't find information on what kind of debug features I can have
>>when after implementing the remote stub. Breakpoint, watchpoint,
>>single step?
http://sources.redhat.com/gdb/onlinedocs/gdb_33.html
This doc is very clear.

>>3) Not sure how to write a download program to download executable
>>from target to host in a debug session.
I think if your stub on VM support GDBRSP write memory command M, you
can use GDB command load do it.


  parent reply	other threads:[~2006-08-21 13:35 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 [this message]
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
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=daef60380608210634q7085cda2p3faeef2a517fd9af@mail.gmail.com \
    --to=teawater@gmail.com \
    --cc=caiqian@gmail.com \
    --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