From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 7996 invoked by alias); 16 Mar 2007 16:36:32 -0000 Received: (qmail 7208 invoked by uid 48); 16 Mar 2007 16:36:19 -0000 Date: Fri, 16 Mar 2007 16:36:00 -0000 Message-ID: <20070316163619.7206.qmail@sourceware.org> From: "cagney at redhat dot com" To: frysk-bugzilla@sourceware.org In-Reply-To: <20070306220819.4163.cagney@redhat.com> References: <20070306220819.4163.cagney@redhat.com> Reply-To: sourceware-bugzilla@sourceware.org Subject: [Bug general/4163] create custom observer double step X-Bugzilla-Reason: AssignedTo Mailing-List: contact frysk-bugzilla-help@sourceware.org; run by ezmlm Precedence: bulk List-Subscribe: List-Post: List-Help: , Sender: frysk-bugzilla-owner@sourceware.org X-SW-Source: 2007-q1/txt/msg00656.txt.bz2 List-Id: ------- Additional Comments From cagney at redhat dot com 2007-03-16 16:36 ------- Yes, concept of "create a custom observer" has morphed into "customize observer". For instance, for syscall-observer, customizing it to just record specific system calls. This in turn, though, leads to further questions: -> what happens if I click on "Syscall Observer" and then click "customize"; is it customizing just the local systemcall observer, or globally. I'm guessing that a customization would apply locally. Perhaps edit, copy buttons are the way to go? Perhaps the interface could better suggest that the observers are being added to a local copy of the pool; for instance (but don't follow :-) the proc-picker makes it clear which processes are of interest by copying them into a separate window -- http://sourceware.org/bugzilla/show_bug.cgi?id=4163 ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.