From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 18230 invoked by alias); 23 Mar 2002 20:14: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 18135 invoked from network); 23 Mar 2002 20:14:34 -0000 Received: from unknown (HELO localhost.redhat.com) (24.112.240.27) by 209.249.29.67 with SMTP; 23 Mar 2002 20:14:34 -0000 Received: from cygnus.com (localhost [127.0.0.1]) by localhost.redhat.com (Postfix) with ESMTP id 5585C3DCE; Sat, 23 Mar 2002 15:14:22 -0500 (EST) Message-ID: <3C9CE21E.2030807@cygnus.com> Date: Sat, 23 Mar 2002 12:14:00 -0000 From: Andrew Cagney User-Agent: Mozilla/5.0 (X11; U; NetBSD macppc; en-US; rv:0.9.8) Gecko/20020210 X-Accept-Language: en-us MIME-Version: 1.0 To: Jim Blandy Cc: gdb-patches@sources.redhat.com, gcc@gcc.gnu.org Subject: Re: RFC: C/C++ preprocessor macro support for GDB References: <20020317062306.CC96D5E9DE@zwingli.cygnus.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2002-03/txt/msg00448.txt.bz2 Hmm, I get the feeling that we're going to end up with: gcc/libcpp and src/libcpp Fun! Are there intermediate steps to this goal? For instance, resolve the directory name and the interfaces GDB will need. That way some of the GDB side can make progress, even if it is initially calling stubbed or ``broken'' libcpp code. enjoy, Andrew