From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Carl Patenaude Poulin <carl.patenaudepoulin@mail.mcgill.ca>,
xen-devel@lists.xen.org
Subject: Re: Check if gdbsx is running
Date: Sat, 26 Dec 2015 23:38:38 +0000 [thread overview]
Message-ID: <567F24FE.8070309@citrix.com> (raw)
In-Reply-To: <CA+v+NpL8B6OKp7WtDtZPCExic328UQPmxdsVca6T=Azo1oPLkg@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 815 bytes --]
On 26/12/2015 23:27, Carl Patenaude Poulin wrote:
> Hi all,
>
> I'm writing some development tools for my team. Given a domain ID,
> is there a way to programmatically check whether gdbsx is running on
> that domain and what port it's running on? I could use something
> like `top -b -n 1 | grep gdbsx` but that seems very brittle.
With a XEN_DOMCTL_getdomaininfo hypercall, "flags & XEN_DOMINF_debugged"
(or xc_dominfo_t.debugged) will tell you whether a debugger is attached
to a domain.
This is the closest I am aware of you being able to get.
Whether gdbsx is running, or what port it is running on, are internal
details to the domain running the debugger and not interesting to Xen.
If you can assume that all debuggers are run in dom0, then some process
list based approach is probably best.
~Andrew
[-- Attachment #1.2: Type: text/html, Size: 1505 bytes --]
[-- Attachment #2: Type: text/plain, Size: 126 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2015-12-26 23:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-26 23:27 Check if gdbsx is running Carl Patenaude Poulin
2015-12-26 23:38 ` Andrew Cooper [this message]
2016-01-04 11:33 ` Ian Campbell
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=567F24FE.8070309@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=carl.patenaudepoulin@mail.mcgill.ca \
--cc=xen-devel@lists.xen.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 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.