From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 13635 invoked by alias); 3 Oct 2003 23:57:05 -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 13627 invoked from network); 3 Oct 2003 23:57:05 -0000 Received: from unknown (HELO zenia.home) (12.223.225.216) by sources.redhat.com with SMTP; 3 Oct 2003 23:57:05 -0000 Received: by zenia.home (Postfix, from userid 5433) id 34FC920766; Fri, 3 Oct 2003 18:56:54 -0500 (EST) To: "Newman, Mark (N-Superior Technical Resource Inc)" Cc: gdb@sources.redhat.com Subject: Re: tracepoint frames References: From: Jim Blandy Date: Fri, 03 Oct 2003 23:57:00 -0000 In-Reply-To: Message-ID: User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-SW-Source: 2003-10/txt/msg00079.txt.bz2 "Newman, Mark (N-Superior Technical Resource Inc)" writes: > The question has come up as to what needs to be collected when a > tracepoint is hit. I understand that a "frame" needs to be > collected. Can someone tell me what a "frame" is. Is it a stack > frame, a trace frame, or what? Well, we do have trace frames; a trace frame is the clump of information collected for a single tracepoint hit. It includes registers, and assorted regions of memory. You can also ask a trace frame to collect things like local variables, arguments, or registers. But all that gets parsed by the code in tracepoint.c and turned into a 'struct collection_list', that's just a set of registers, memory regions, and agent expressions to collect; it's all parsed for you. So at that level, there are no frames any more --- everything is explicit But I don't feel like I've answered the question. In what context did it come up?