From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 15212 invoked by alias); 13 Jan 2002 20:40:03 -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 15140 invoked from network); 13 Jan 2002 20:39:59 -0000 Received: from unknown (HELO localhost.cygnus.com) (24.114.42.213) by sources.redhat.com with SMTP; 13 Jan 2002 20:39:59 -0000 Received: from cygnus.com (localhost [127.0.0.1]) by localhost.cygnus.com (Postfix) with ESMTP id 50EA13D1F; Sun, 13 Jan 2002 15:39:57 -0500 (EST) Message-ID: <3C41F09C.7040308@cygnus.com> Date: Sun, 13 Jan 2002 12:40:00 -0000 From: Andrew Cagney User-Agent: Mozilla/5.0 (X11; U; NetBSD macppc; en-US; rv:0.9.7) Gecko/20020103 X-Accept-Language: en-us MIME-Version: 1.0 To: Keith Seitz Cc: gdb-patches@sources.redhat.com Subject: Re: [RFA] stack.c: move address printing into hook (fwd) References: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2002-01/txt/msg00357.txt.bz2 > Of course, if you just mention to me how you'd like it to be solved, I > would be more than happy to try to implement something to your liking... > ;-) The theory is simple. The code building the stop message should be separate to the code determining why the target stopped. That way the CLI and the MI/Insight can each separatly query for the stop reason. This in turn means that, for Insight, your logic can read: when (target stopped event) get stop reason process stop reason I think I've now attempted this three times and three times it has beaten me :-( The way GDB constructs its stop info is totally screwed up. Andrew