public inbox for archer@sourceware.org
 help / color / mirror / Atom feed
From: Chris Moller <cmoller@redhat.com>
To: Jan Kratochvil <jan.kratochvil@redhat.com>
Cc: archer@sourceware.org
Subject: Re: Proof-of-concept on fd-connected linux-nat.c server
Date: Sat, 09 May 2009 19:50:00 -0000	[thread overview]
Message-ID: <4A05DE6C.8000508@redhat.com> (raw)
In-Reply-To: <20090509151556.GA17252@host0.dyn.jankratochvil.net>

[-- Attachment #1: Type: text/plain, Size: 1644 bytes --]

Hi, Jan,

Thanks for the effort, but...

I talked to Eric about gdb/froggy/utrace last week and after a while it
became apparent that my impression of what I should be doing--a
wholesale replacement of ptrace/waitpid in synchronous gdb--wasn't what
he had in mind.    Apparently, what I was supposed to have been doing is
working on using froggy/utrace in asynchronous free-running threads. 
That's make vastly more sense than the wholesale replacement
thing--basically reimplementing ptrace/waitpid over a file descriptor
would add almost no functionality, would likely hurt performance at
least a little, and certainly add instability to existing function.  The
asynchronous free-running thread thing, on the other hand, takes
advantage of features of utrace/froggy not readily available with
ptrace/waitpid and is much more in keeping with what I designed froggy
for in the first place--the wholesale replacement thing would basically
have entailed throwing out more than half of froggy, and the more
interesting bits of it at that.

So, for about the third time, I'm throwing out a fair amount of work and
starting over.  This time, instead of forking froggy--which was going to
eliminate the asynchronous major bits of it that gdb wouldn't have
needed--I'm going to add direct file descriptor access to the main
branch and go with that.

Chris

Jan Kratochvil wrote:
> Hi Chris,
>
> tried to implement the file-descriptor based client for GDB as a possible
> client for the kernel module which would interface utrace.  Based on my mail:
>   http://sourceware.org/ml/archer/2009-q1/msg00257.html
>   



[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 251 bytes --]

  reply	other threads:[~2009-05-09 19:50 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-09 15:16 Jan Kratochvil
2009-05-09 19:50 ` Chris Moller [this message]
2009-05-10  9:19   ` Jan Kratochvil
2009-05-10 10:25 ` Pedro Alves
2009-05-10 14:59   ` Jan Kratochvil
2009-05-10 15:42     ` Pedro Alves

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=4A05DE6C.8000508@redhat.com \
    --to=cmoller@redhat.com \
    --cc=archer@sourceware.org \
    --cc=jan.kratochvil@redhat.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 read-only IMAP folder(s) and NNTP newsgroup(s).