public inbox for
 help / color / mirror / Atom feed
From: Roland McGrath <>
To: Oleg Nesterov <>
Subject: Re: gdbstub initial code, v16
Date: Tue, 16 Nov 2010 20:02:00 -0000	[thread overview]
Message-ID: <> (raw)
In-Reply-To: Oleg Nesterov's message of  Monday, 15 November 2010 20:05:37 +0100 <>

> Well. I can't say this change is good. Because ugdb uses (unexported)
> arch_ptrace() to set debugregs in a very much x86-specific way. However,
> I do not see what else can I do.

That kludge is unworkable in several ways.  It is just not worth pursuing.
Just use hw_breakpoint on kernels that have it, and don't try to support
the feature on kernels that don't.

> Say, should I implement vRun? From the very beginnig, I hate the idea
> to exec the target from kernel space, but otoh I'm afraid this is
> important for gdb users.

We've also vaguely discussed doing some hybrid solution where gdb does
something different for "run".  If you can do a kludge to implement vRun
fairly quickly and it works OK--including that it remains possible for
ugdb to be a module--then go ahead.  If that is too ungainly, or is just
plain infeasible (which I think it might be), then don't bend over
backwards for it.  We may have reached the end of what it's possible to
get done at all sensibly without more active involvement from the GDB team.


  reply	other threads:[~2010-11-16 20:02 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-15 19:12 Oleg Nesterov
2010-11-16 20:02 ` Roland McGrath [this message]
     [not found] ` <>
     [not found]   ` <>
     [not found]     ` <>
     [not found]       ` <>
     [not found]         ` <>
     [not found]           ` <>
     [not found]             ` <>
2011-02-23 15:51               ` safe PTRACE_ATTACH Jan Kratochvil
2011-02-23 17:24                 ` Oleg Nesterov

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \

* 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 read-only IMAP folder(s) and NNTP newsgroup(s).