From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 7373 invoked by alias); 11 Mar 2010 00:11:25 -0000 Received: (qmail 7363 invoked by uid 22791); 11 Mar 2010 00:11:24 -0000 X-SWARE-Spam-Status: No, hits=-2.5 required=5.0 tests=AWL,BAYES_00 X-Spam-Check-By: sourceware.org Received: from mail.codesourcery.com (HELO mail.codesourcery.com) (38.113.113.100) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Thu, 11 Mar 2010 00:11:19 +0000 Received: (qmail 17220 invoked from network); 11 Mar 2010 00:11:18 -0000 Received: from unknown (HELO orlando.localnet) (pedro@127.0.0.2) by mail.codesourcery.com with ESMTPA; 11 Mar 2010 00:11:18 -0000 From: Pedro Alves To: Daniel Jacobowitz Subject: Re: [PING] [RFC-v3] Add windows Thread Information Block Date: Thu, 11 Mar 2010 00:11:00 -0000 User-Agent: KMail/1.12.2 (Linux/2.6.31-19-generic; KDE/4.3.2; x86_64; ; ) Cc: Pierre Muller , gdb-patches@sourceware.org References: <000901c9f5ef$4ee06f10$eca14d30$@u-strasbg.fr> <000c01cac0a0$3935fbe0$aba1f3a0$@muller@ics-cnrs.unistra.fr> <20100310233035.GA2056@caradoc.them.org> In-Reply-To: <20100310233035.GA2056@caradoc.them.org> MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <201003110011.15690.pedro@codesourcery.com> X-IsSubscribed: yes Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org X-SW-Source: 2010-03/txt/msg00406.txt.bz2 On Wednesday 10 March 2010 23:30:40, Daniel Jacobowitz wrote: > On Wed, Mar 10, 2010 at 11:22:51PM +0100, Pierre Muller wrote: > > OK, I start to remember now, > > you said that TARGET_OBJECT_DATA should use xml syntax for > > all data transmission, what that it? > > My two cents... the issue isn't that you aren't using XML, but that > you're using TARGET_OBJECT_OSDATA. That's for information about the > operating system, like the list of all running processes, not about > the current process. > > Pedro, this raises an interesting question. Suppose Pierre added a > new qXfer object. How would he indicate to a remote target which > process's object was requested? This may be something already > handled, but I don't know the answer. The "general thread" is reused for target objects. There's no way in the protocol to select a process as context, other than selecting a thread of it. Example, TARGET_OBJECT_SIGNAL_INFO (for $_siginfo) transfers from the remote protocol current|general thread. I think we'd do the same for this? A non-thread specific xfer example: TARGET_OBJECT_AUXV transfers from the process of the currently selected thread. Some packets specify the thread/process explicitly. For example, the `qGetTLBAddr' packet alternative would do like `qGetTLSAddr' does: `qGetTLBAddr:TID...' if multiprocess is off, or `qGetTLBAddr:pPID.TID...' if multiprocess is on. -- Pedro Alves