From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 32716 invoked by alias); 9 May 2009 19:50:21 -0000 Mailing-List: contact archer-help@sourceware.org; run by ezmlm Sender: Precedence: bulk List-Post: List-Help: List-Subscribe: List-Id: Received: (qmail 32666 invoked by uid 22791); 9 May 2009 19:50:20 -0000 X-SWARE-Spam-Status: No, hits=-2.5 required=5.0 tests=AWL,BAYES_00,SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: sourceware.org Message-ID: <4A05DE6C.8000508@redhat.com> Date: Sat, 09 May 2009 19:50:00 -0000 From: Chris Moller User-Agent: Thunderbird 2.0.0.12 (X11/20080226) MIME-Version: 1.0 To: Jan Kratochvil CC: archer@sourceware.org Subject: Re: Proof-of-concept on fd-connected linux-nat.c server References: <20090509151556.GA17252@host0.dyn.jankratochvil.net> In-Reply-To: <20090509151556.GA17252@host0.dyn.jankratochvil.net> Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enigC34E936DC910482C15C7F45E" X-SW-Source: 2009-q2/txt/msg00080.txt.bz2 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enigC34E936DC910482C15C7F45E Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-length: 1617 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.=20 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 m= ail: > http://sourceware.org/ml/archer/2009-q1/msg00257.html >=20=20=20 --------------enigC34E936DC910482C15C7F45E Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" Content-length: 251 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iD8DBQFKBd5zmpMCeQnqFMkRArjoAJ0QP3hezWobUZPJRTzTwXfZHKcuMACeLWBK 65b+ZTmd2SFQAJrpHvLzVDU= =MOZk -----END PGP SIGNATURE----- --------------enigC34E936DC910482C15C7F45E--