From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 1230 invoked by alias); 14 Apr 2003 17:04:24 -0000 Mailing-List: contact gdb-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sources.redhat.com Received: (qmail 1039 invoked from network); 14 Apr 2003 17:04:20 -0000 Received: from unknown (HELO mail-out1.apple.com) (17.254.0.52) by sources.redhat.com with SMTP; 14 Apr 2003 17:04:20 -0000 Received: from mailgate2.apple.com (A17-129-100-225.apple.com [17.129.100.225]) by mail-out1.apple.com (8.12.9/8.12.9) with ESMTP id h3EH4K3h023552 for ; Mon, 14 Apr 2003 10:04:20 -0700 (PDT) Received: from scv2.apple.com (scv2.apple.com) by mailgate2.apple.com (Content Technologies SMTPRS 4.2.1) with ESMTP id ; Mon, 14 Apr 2003 10:04:19 -0700 Received: from apple.com (inghji.apple.com [17.201.22.240]) by scv2.apple.com (8.12.9/8.12.9) with ESMTP id h3EH4IbN015362; Mon, 14 Apr 2003 10:04:19 -0700 (PDT) Date: Mon, 14 Apr 2003 17:04:00 -0000 Subject: Re: Add fullname to breakpoint output Content-Type: text/plain; charset=US-ASCII; format=flowed Mime-Version: 1.0 (Apple Message framework v551) Cc: gdb@sources.redhat.com To: Andrew Cagney From: Jim Ingham In-Reply-To: <3E9A3599.9080100@redhat.com> Message-Id: <217F54D2-6E9B-11D7-BECB-00039379E320@apple.com> Content-Transfer-Encoding: 7bit X-SW-Source: 2003-04/txt/msg00130.txt.bz2 To my mind, as long as you have "ui_out_text" sprinkled amongst the result accumulating statements in "core" gdb, you have CLI code embedded in the core gdb functionality. After all, the "text" output was just a clever way to continue formatting stuff up for the CLI without polluting the MI output. But having it there means command output can't be changed without potentially messing up the CLI output - the two are still intimately linked. disasm.c has a bunch of ui_out_text calls. Jim On Sunday, April 13, 2003, at 09:14 PM, Andrew Cagney wrote: > >> Yes, this is a desirable goal. Have you thought about how to do this? > >> The best way I can think of is to have a new ui_out that builds up an >> intermediate representation for results that is easy to access >> randomly - making up real lists & dictionaries from the >> ui_out_field_xxx and list & table stuff. Then we could banish >> ui_out_text & friends to the CLI commands to take the whole result, >> pull bits out in the order they expected, and annotate them with >> text, newlines, etc, in order to make a nice display. >> In practice, this will be gnarly to get right, but you could do it >> incrementally by getting the intermediate rep. ui_out working, then >> fix the CLI commands one by one by swapping in the new ui_out for >> those commands you had fixed, and using the old CLI one for the >> commands you hadn't gotten working... > > I don't know that anything that complicated is needed. disasm.c > worked out pretty well. > > Andrew > > > -- Jim Ingham jingham@apple.com Developer Tools Apple Computer