xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Huibin QIAN <qianhb@huawei.com>
To: James Harper <james.harper@bendigoit.com.au>
Cc: xen-devel@lists.xensource.com
Subject: Remote debug quetion
Date: Thu, 28 Jan 2010 20:22:50 +0800	[thread overview]
Message-ID: <001801caa014$9bb08f30$d738a60a@china.huawei.com> (raw)
In-Reply-To: 20100128080636.GW2861@reaktio.net


[-- Attachment #1.1: Type: text/plain, Size: 1949 bytes --]

Hey James.

I follow your step of setup remote debug enviroment.

But I cant connect the DomU which to be debuged by WinDBG.

Attechment shows the status of 'HW Virtual Serial Port'.

Can your have a look at the attechment and give some advise?

Best Regards
Huibin

  ----- Original Message ----- 
  From: Pasi Kärkkäinen 
  To: Huibin QIAN 
  Cc: xen-users@lists.xensource.com 
  Sent: Thursday, January 28, 2010 4:06 PM
  Subject: Re: [Xen-users] Remote debug quetion


  On Thu, Jan 28, 2010 at 03:50:16PM +0800, Huibin QIAN wrote:
  > 
  > 
  >    Thanks Pasi,
  > 
  >    That's very useful,But I still can't cennectted to the DomU tobe debuged.
  > 
  >    It seems like the 'xm console DomU' works not properly.
  > 
  >    The attechment shows the server state is 'Closed' and no data received
  > 
  >     And suggestion?
  > 

  I haven't used it myself so unfortunately no..
  I think you should ask on xen-devel mailinglist!

  Btw what kind of driver are you developing? 

  -- Pasi

  > 
  > 
  >      ----- Original Message -----
  >      From: [1]Pasi Kärkkäinen
  >      To: [2]Huibin QIAN
  >      Cc: [3]xen-users@lists.xensource.com
  >      Sent: Wednesday, January 27, 2010 10:17 PM
  >      Subject: Re: [Xen-users] Remote debug quetion
  >      On Wed, Jan 27, 2010 at 05:14:11PM +0800, Huibin QIAN wrote:
  >      >    Hey all,
  >      >
  >      >    I plan to use windbg tool to do remote debug my Windows PV Driver.
  >      >    I'm confused how to setup the enviroment.
  >      >
  >      >    Any Advice?
  >      >
  > 
  >      IIRC GPLPV wiki page has some info how to set it up..
  > 
  >      -- Pasi
  > 
  > References
  > 
  >    Visible links
  >    1. pasik@iki.fi
  > mailto:pasik@iki.fi
  >    2. qianhb@huawei.com
  > mailto:qianhb@huawei.com
  >    3. xen-users@lists.xensource.com
  > mailto:xen-users@lists.xensource.com


[-- Attachment #1.2: Type: text/html, Size: 4666 bytes --]

[-- Attachment #2: 未命名.JPG --]
[-- Type: image/jpeg, Size: 37471 bytes --]

[-- Attachment #3: Type: text/plain, Size: 138 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

       reply	other threads:[~2010-01-28 12:22 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <000d01ca9f31$1971c220$d738a60a@china.huawei.com>
     [not found] ` <20100127141701.GN2861@reaktio.net>
     [not found]   ` <006401ca9fee$8844e610$d738a60a@china.huawei.com>
     [not found]     ` <20100128080636.GW2861@reaktio.net>
2010-01-28 12:22       ` Huibin QIAN [this message]
2010-02-01 11:11         ` Remote debug quetion James Harper

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='001801caa014$9bb08f30$d738a60a@china.huawei.com' \
    --to=qianhb@huawei.com \
    --cc=james.harper@bendigoit.com.au \
    --cc=xen-devel@lists.xensource.com \
    /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 NNTP newsgroup(s).