From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 22417 invoked by alias); 19 Feb 2003 18:05:37 -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 22409 invoked from network); 19 Feb 2003 18:05:37 -0000 Received: from unknown (HELO localhost.redhat.com) (172.16.49.200) by 172.16.49.205 with SMTP; 19 Feb 2003 18:05:37 -0000 Received: from redhat.com (localhost [127.0.0.1]) by localhost.redhat.com (Postfix) with ESMTP id 9DD072E96; Wed, 19 Feb 2003 13:10:22 -0500 (EST) Message-ID: <3E53C88E.90807@redhat.com> Date: Wed, 19 Feb 2003 18:05:00 -0000 From: Andrew Cagney User-Agent: Mozilla/5.0 (X11; U; NetBSD i386; en-US; rv:1.0.2) Gecko/20030217 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Joel Brobecker Cc: gdb-patches@sources.redhat.com Subject: Re: Re-initializing a list after the control returns to gdb... References: <20030219020101.GI2105@gnat.com> <3E53B97A.4090809@redhat.com> <20030219175056.GP2105@gnat.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2003-02/txt/msg00426.txt.bz2 >> You've the `observer' problem. > > > Just like when you are sick, you already feel better when you know which > disease you have contracted :). > > >> GDB's observer code is very primative. A combination of gdb-events >> (needs direction) and chained hooks (see target_new_objfile_hook). >> >> I suspect what you really want is a `target changed' event. > > > I need to update the task list every time the inferior stops and > the control returns to the user. I think the `target change' event > is not exactly what I would need? The code relies on global state so I think `target changed' is better - that way you know that your state is up-to-date. From memory, right now we've actually memory_changed and registers_changed (I think they should be merged). There is also a target run hook that insight uses. > Do we have a list of currently supported events? Is there a framework > for implementing these events? That's the problem (you said sick), we've three: - gdb-events - chained hooks - simple hooks gdb-events started on the problem but lost direction. Andrew