From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 24674 invoked by alias); 26 Aug 2002 19:48:06 -0000 Mailing-List: contact gdb-patches-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sources.redhat.com Received: (qmail 24641 invoked from network); 26 Aug 2002 19:48:04 -0000 Received: from unknown (HELO valrhona.uglyboxes.com) (64.1.192.220) by sources.redhat.com with SMTP; 26 Aug 2002 19:48:04 -0000 Received: from localhost.localdomain (IDENT:KeyOWmIa8E1q2YP5Y/QR5zNdtwh1wu7c@localhost.localdomain [127.0.0.1]) by valrhona.uglyboxes.com (8.11.6/8.11.6) with ESMTP id g7QJogY10991 for ; Mon, 26 Aug 2002 12:50:42 -0700 Date: Mon, 26 Aug 2002 12:55:00 -0000 From: Keith Seitz X-X-Sender: keiths@valrhona.uglyboxes.com To: gdb-patches@sources.redhat.com Subject: Re: [RFA] gdb-events.sh: selected-frame-level-changed event In-Reply-To: <3D696004.9060304@ges.redhat.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-SW-Source: 2002-08/txt/msg00860.txt.bz2 On Sun, 25 Aug 2002, Andrew Cagney wrote: > Ok. Committed. > Any thoughts on how selected-thread events will be handled? They also > change the selected-fraome. I think that like many events, selected-thread change events imply that a whole bunch of things have changed, too. For example, a target-stop event (which we don't really issue as an event like the rest, but it is really just an event), automatically implies that the selected frame, thread, and other things have changed, yet we do not issue events for all of these. I believe that the selected-thread event is the same. In any case, I'm sure that we've done things wrong. In fact, I'd be willing to bet that we have. But one small step forward is better than none. We can always address issues as they appear, which is one of the nice things about the event mechanisms: GDB itself doesn't use them! They are UI-specific and quite isolated. :-) Keith