From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 6877 invoked by alias); 1 Jan 2004 22:56:16 -0000 Mailing-List: contact gdb-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sources.redhat.com Received: (qmail 6868 invoked from network); 1 Jan 2004 22:56:13 -0000 Received: from unknown (HELO nevyn.them.org) (66.93.172.17) by sources.redhat.com with SMTP; 1 Jan 2004 22:56:13 -0000 Received: from drow by nevyn.them.org with local (Exim 4.30 #1 (Debian)) id 1AcBie-0003lo-CT; Thu, 01 Jan 2004 17:55:08 -0500 Date: Thu, 01 Jan 2004 22:56:00 -0000 From: Daniel Jacobowitz To: Ramana Radhakrishnan Cc: Andrew Cagney , gdb@sources.redhat.com, ankit thukral Subject: Re: [RFC] Addition of remote tracepoints to gdb / gdbserver. Message-ID: <20040101225507.GA14446@nevyn.them.org> Mail-Followup-To: Ramana Radhakrishnan , Andrew Cagney , gdb@sources.redhat.com, ankit thukral References: <3FF49153.50100@codito.com> <20040101214655.GB12798@nevyn.them.org> <3FF49E8A.7020403@codito.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3FF49E8A.7020403@codito.com> User-Agent: Mutt/1.5.1i X-SW-Source: 2004-01/txt/msg00021.txt.bz2 On Fri, Jan 02, 2004 at 03:56:18AM +0530, Ramana Radhakrishnan wrote: > Now the remote side would have to understand the target floating point > format / collect the values for > the same and hence the actual computation would have to be target > specific .2 options > a. do all calculations in gdbserver > b. collect all byte sequences and take care of it in gdb. > > Option b seems less expensive. Yes, but sometimes it's not enough. In the example I gave you'd have to do the memory reference at trace collection time. But I don't think it's a real problem so option b is probably fine. > That'd be PTRACE_EXIT_EVENT in the modern kernels.?Something that I > missed out in my earlier mails. Right. -- Daniel Jacobowitz MontaVista Software Debian GNU/Linux Developer