From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 26342 invoked by alias); 5 Apr 2010 11:04:39 -0000 Received: (qmail 26231 invoked by uid 22791); 5 Apr 2010 11:04:33 -0000 X-SWARE-Spam-Status: No, hits=-1.9 required=5.0 tests=BAYES_00,T_RP_MATCHES_RCVD 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; Mon, 05 Apr 2010 11:04:29 +0000 Received: (qmail 16212 invoked from network); 5 Apr 2010 11:04:27 -0000 Received: from unknown (HELO orlando.localnet) (pedro@127.0.0.2) by mail.codesourcery.com with ESMTPA; 5 Apr 2010 11:04:27 -0000 From: Pedro Alves To: Stan Shebs Subject: Re: tracing broken if target doesn't do disconnected tracing Date: Mon, 05 Apr 2010 11:04:00 -0000 User-Agent: KMail/1.12.2 (Linux/2.6.31-20-generic; KDE/4.3.2; x86_64; ; ) Cc: gdb-patches@sourceware.org References: <201004050101.02067.pedro@codesourcery.com> <4BB937EC.6080303@codesourcery.com> In-Reply-To: <4BB937EC.6080303@codesourcery.com> MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <201004051204.25151.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-04/txt/msg00072.txt.bz2 On Monday 05 April 2010 02:07:56, Stan Shebs wrote: > I'm thinking that this is in some ways like the circular trace buffer > flag, and could be reasonably made accessible via the trace_status > structure. Unless you're just dying to do this yourself :-) , I'll take > care of the two together. Please, be my guest. :-) > (I can see where this is going longterm - struct trace_status is > effectively a host-side copy of the agent's state, echoed back in > response to any instructions that GDB sends down.) I'd only suggest you keep in mind what will happen when we define how tracing works with multi-process, as we'll be working on that soonish. That is, whether with multi-process, there will be a trace status object per process, while supporting disconnected tracing or not sounds like a target (debug interface) wide attribute. -- Pedro Alves