From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 20197 invoked by alias); 16 Mar 2007 20:46:49 -0000 Received: (qmail 20152 invoked by uid 48); 16 Mar 2007 20:46:39 -0000 Date: Fri, 16 Mar 2007 20:46:00 -0000 Message-ID: <20070316204639.20151.qmail@sourceware.org> From: "swagiaal 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/msg00662.txt.bz2 List-Id: ------- Additional Comments From swagiaal at redhat dot com 2007-03-16 20:46 ------- Some suggestions as a result of discussion between me and Andrew: Gobalizing Observers over the entire session. This means having a global list of observers which watch all procs/threads in the current session, and allowing the user to choose which ones are on/off. Changes would then be a customization of the observers. This means eleminating the metaphore that observers are added to procs/threads of course. It also has some performace implications. Anyways its a good topic for the next meeting. -- 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.