From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 21038 invoked by alias); 21 Feb 2007 14:32:07 -0000 Received: (qmail 21031 invoked by uid 22791); 21 Feb 2007 14:32:06 -0000 X-Spam-Status: No, hits=-1.4 required=5.0 tests=AWL,BAYES_40,SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: sourceware.org Received: from mx1.redhat.com (HELO mx1.redhat.com) (66.187.233.31) by sourceware.org (qpsmtpd/0.31) with ESMTP; Wed, 21 Feb 2007 14:31:48 +0000 Received: from int-mx1.corp.redhat.com (int-mx1.corp.redhat.com [172.16.52.254]) by mx1.redhat.com (8.13.1/8.13.1) with ESMTP id l1LEVjic009714 for ; Wed, 21 Feb 2007 09:31:45 -0500 Received: from pobox.corp.redhat.com (pobox.corp.redhat.com [10.11.255.20]) by int-mx1.corp.redhat.com (8.13.1/8.13.1) with ESMTP id l1LEVj3r023156 for ; Wed, 21 Feb 2007 09:31:45 -0500 Received: from [127.0.0.1] (sebastian-int.corp.redhat.com [172.16.52.221]) by pobox.corp.redhat.com (8.13.1/8.13.1) with ESMTP id l1LEVhqk001216 for ; Wed, 21 Feb 2007 09:31:44 -0500 Message-ID: <45DC57C3.1030700@redhat.com> Date: Wed, 21 Feb 2007 14:32:00 -0000 From: Andrew Cagney User-Agent: Thunderbird 1.5.0.9 (X11/20070102) MIME-Version: 1.0 To: frysk Subject: Minutes 2007-02-14 @9:30 US-EST References: <45D145C8.9050202@redhat.com> <45D22A1B.20204@redhat.com> In-Reply-To: <45D22A1B.20204@redhat.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Mailing-List: contact frysk-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Post: List-Help: , Sender: frysk-owner@sourceware.org X-SW-Source: 2007-q1/txt/msg00153.txt.bz2 Present: Rick, Phil, Mike, Cagney, Elena, Moller, Kris, Stan, Tim, Jonathan, Mark, Sami, Nurdin (snow in Toronto meant some people arrived late) HPD command line. ----------------------- Stan and Tim provided a walk through. tab-completion: - per bug(?), for a full completion, should append a space as that is the next thing the user will type, vis: help -> help_ attach: - HPD syntax is <>, per bug (?) the <> is redundant, and just the list of pids need to be provided - attach needs to provide direct feed back that the operation is completed, for instance by displaying the line of the main thread print: Working in some cases. Need to expose code to more stress testing. help: Simple help works, but <> doesn't display the more specific information. breakpoint: The syntax needs to review the HPD, in particular how to specify file#line or foo(int) or file#foo(int) or #glibc.so#printf or ...; the syntax is powerful and follow pattern matching (but may contain limitations). Most important the wart of having to specify 'foo(int)', caused by using ':' as the breakpoint separator needs to be avoidable. additional comments and notes: threads and thread groups? The HPD describes how the prompt can change, reflecting which threads an operation will apply to. For instance: [1.1,1.2]> break foo applies the breakpoint to both threads. transcript mechanism? is there a command for capturing operations (hpd defines one) so that it is possible to capture how people are trying to use the interface. registers? Brief discussion about adding a way to print registers; was noted that this requires core changes, in particular changing frysk.proc.Task.registers so that they are described in terms of frysk.value.Value - i.e., the registers have a type. disassembler? Brief discussion about adding a disassembler; was noted that frysk.rt.StackFrame will need to be modified adding a frysk.rt.Symbol object that contains the function address, name, and bound; and then disassemble based on that range. ----- Custom Observer: Meta-discussion: is the custom observer at the right level. For instance, is it reasonable to be trying to implement all possible functionality graphically, or provide a basic edit menu and then have more complicated events added as custom event handling code. Conclusion: custom observer is at the right level, with edits. In particular complicated event trigers should be handled using programming interface. -> default should be to capture information, but not try to log it. For instance, don't write to log window, instead let user examine event using monitor view. -> rename observer to "event"; its an event trigger that is being selected -> +/- buttons in filter et.al. confused; for instance, why does the first action have a "+"; suggest looking at thunderbird and evolution's filter windows -> 'ok' at bottom should make it clear what clicking on it does -> action arguments should be disabled when they don't apply; for instance, catch stack backtrace requires no argument -> "filter" and what it is doing misleading; should be clear that a filter is a customization of the event