All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kip Macy <kmacy@fsmware.com>
To: Ryan Harper <ryanh@us.ibm.com>
Cc: xen-devel@lists.sourceforge.net
Subject: Re: XenDebugger-HOWTO
Date: Mon, 17 Jan 2005 18:28:38 -0800 (PST)	[thread overview]
Message-ID: <20050117181906.J81222@demos.bsdclusters.com> (raw)
In-Reply-To: <20050118000402.GA6880@luffy.austin.ibm.com>

nsplitd allows you to use one serial port for both the debugger and the
console. It multiplexes the two by setting the high-bit on one and not
the other.

Sample - machine is named 'larry'
from /etc/services:
shemp0          6056/tcp                        # shemp console
shempnsplit     12016/tcp                       # shemp nsplit service

6056 is the port on the actual console server - 12016 is the port I
connect to on this machine to connect to the console

from /etc/xinetd.d/nsplit:

  service shempnsplit
  {
        socket_type             = stream
        protocol                = tcp
        wait                    = no
        user                    = root
        server                  = /usr/sbin/in.nsplitd
        server_args             = raidqa-cpt1:shemp0
        disable                 = no

  }


raidqa-cpt1 is the name of the console server -


I connect to shemp's console by on larry 12016, I connect gdb with
(gdb) target remote shemp:2345


Just to warn you. I've found PDB to be completely broken for the past
four months. If you get it to work, let me know what your setup is. If
you are debugging DOM0 or xen, it is pretty much your only option. If
you are debugging a guest, my debug patches work *much* better.



					-Kip






On Mon, 17 Jan 2005, Ryan Harper wrote:

> I've been trying to get the XenDebugger running on the unstable tree.
> After compiling xen with debugging=y ( and some patches ), I started
> following the XenDebugger-Howto, but something is missing.
>
> How does nsplitd connect to the serial line going into Xen?
>
> Looking at the diagram entitled Setup:
>
> Setup
> -----
>
>  +-------+ telnet +-----------+ serial +-------+
>  |  GDB  |--------|  nsplitd  |--------|  Xen  |
>  +-------+        +-----------+        +-------+
>
> it would seem that nsplitd connects a gdb-telnet session to the serial
> connection into Xen running with pdb on.  However, if you examine
> nsplitd code there is nothing related to serial at all, just sockets.
>
> Looking further into the howto, I set up my xinetd conf as instructed
> and added the two lines to /etc/services:
>
> hostname$ egrep 'wcons00|nsplit1' /etc/services
> wcons00         9600/tcp        # Wanda remote console
> nsplit1         12010/tcp       # Nemesis console splitter ports.
>
> What is the Wanda remote console?
>
> I'm guessing that Wanda is the missing piece that connects the local
> serial port to the network.  If so, where is Wanda?  And if not, what am
> I missing that connects the network connection (gdb telnet) to the
> serial line into xen?
>
> Ryan Harper
>
>
> -------------------------------------------------------
> The SF.Net email is sponsored by: Beat the post-holiday blues
> Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
> It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/xen-devel
>


-------------------------------------------------------
The SF.Net email is sponsored by: Beat the post-holiday blues
Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt

  reply	other threads:[~2005-01-18  2:28 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-18  0:04 XenDebugger-HOWTO Ryan Harper
2005-01-18  2:28 ` Kip Macy [this message]
2005-01-18  5:07   ` Correction XenDebugger-HOWTO Kip Macy
  -- strict thread matches above, loose matches on Subject: below --
2005-01-18 15:55 XenDebugger-HOWTO Ryan 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=20050117181906.J81222@demos.bsdclusters.com \
    --to=kmacy@fsmware.com \
    --cc=ryanh@us.ibm.com \
    --cc=xen-devel@lists.sourceforge.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.