From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 32095 invoked by alias); 2 Oct 2002 14:58:22 -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 32087 invoked from network); 2 Oct 2002 14:58:21 -0000 Received: from unknown (HELO mx1.redhat.com) (66.187.233.31) by sources.redhat.com with SMTP; 2 Oct 2002 14:58:21 -0000 Received: from int-mx1.corp.redhat.com (int-mx1.corp.redhat.com [172.16.52.254]) by mx1.redhat.com (8.11.6/8.11.6) with ESMTP id g92EdUi09247 for ; Wed, 2 Oct 2002 10:39:30 -0400 Received: from pobox.corp.redhat.com (pobox.corp.redhat.com [172.16.52.156]) by int-mx1.corp.redhat.com (8.11.6/8.11.6) with ESMTP id g92EwKf02170; Wed, 2 Oct 2002 10:58:20 -0400 Received: from valrhona.uglyboxes.com (IDENT:x2z+WsreUxlLNpSqeQjzygfvJ5EC7QGR@vpn50-50.rdu.redhat.com [172.16.50.50]) by pobox.corp.redhat.com (8.11.6/8.11.6) with ESMTP id g92EwJ904500; Wed, 2 Oct 2002 10:58:20 -0400 Date: Wed, 02 Oct 2002 07:58:00 -0000 From: Keith Seitz X-X-Sender: keiths@valrhona.uglyboxes.com To: Jim Ingham cc: gdb-patches@sources.redhat.com Subject: Re: [patch rfa:doco rfc:NEWS] mi1 -> mi2; rm mi0 In-Reply-To: <1878A518-D5A0-11D6-BB61-00039379E320@apple.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-SW-Source: 2002-10/txt/msg00050.txt.bz2 On Tue, 1 Oct 2002, Jim Ingham wrote: > I don't want a tight coupling in TIME, or in the output sequence. I > want meta-info which tells me with 100% certainty that this result is > the result of command foo, that I sent some time in the past, precisely > so I DON'T have to rely on anything about the sequencing of input or > output to make this connection. Ok, but this is exactly what I don't understand: what does it matter where the breakpoint comes from? All that matters is that you have issued a command, and you don't do anything out of the normaluntil an event from GDB telling you that it has set a breakpoint. You just sit in your event loop waiting for any event (GUI, paint, GDB, blah blah blah). Insight has used a method exactly like this now for over a year. When a breakpoint is set, Insight tells gdb to set it. It then returns to the command loop. It doesn't do anything else. It's not waiting for anything. When the breakpoint event comes from gdb, it creates its breakpoint object and passes it around. The source window gets it and places a breakpoint at the appropriate place. I can only assume that you've got private data that you need to associate with commands and that this data is lost when returning to the event loop. Please help me understand why it is so important to know exactly what command prompted a breakpoint event. I still just don't get it. Can you give me a specific example of when it would be useful to know that command A elicited breakpoint event A' instead of command B? Sorry. Keith