From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 20058 invoked by alias); 10 Nov 2005 19:13:29 -0000 Mailing-List: contact gcc-help-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-help-owner@gcc.gnu.org Received: (qmail 20012 invoked by uid 22791); 10 Nov 2005 19:13:26 -0000 Received: from fencepost.gnu.org (HELO fencepost.gnu.org) (199.232.76.164) by sourceware.org (qpsmtpd/0.30-dev) with ESMTP; Thu, 10 Nov 2005 19:13:26 +0000 Received: from monty-python.gnu.org ([199.232.76.173]) by fencepost.gnu.org with esmtp (Exim 4.34) id 1EaHqh-0005if-G0 for gcc-help@gnu.org; Thu, 10 Nov 2005 14:13:22 -0500 Received: from Debian-exim by monty-python.gnu.org with spam-scanned (Exim 4.34) id 1EaHqh-0006jr-58 for gcc-help@gnu.org; Thu, 10 Nov 2005 14:12:39 -0500 Received: from [202.37.101.8] (helo=viper.snap.net.nz) by monty-python.gnu.org with esmtp (Exim 4.34) id 1EaHqg-0006jk-OR for gcc-help@gnu.org; Thu, 10 Nov 2005 14:12:39 -0500 Received: from kahikatea.snap.net.nz (p84-tnt1.snap.net.nz [202.124.110.84]) by viper.snap.net.nz (Postfix) with ESMTP id 46F65731028; Fri, 11 Nov 2005 08:12:36 +1300 (NZDT) Received: by kahikatea.snap.net.nz (Postfix, from userid 500) id 9498D83AE; Fri, 11 Nov 2005 08:12:55 +1300 (NZDT) From: Nick Roberts MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <17267.39863.36467.881393@kahikatea.snap.net.nz> Date: Thu, 10 Nov 2005 19:13:00 -0000 To: Daniel Berlin Cc: John Love-Jensen , gcc-help@gnu.org Subject: Re: Macro expansion: GCC 3.4.4 In-Reply-To: <1131630516.7443.6.camel@linux.site> References: <17265.25812.936653.920077@kahikatea.snap.net.nz> <17266.29709.941044.86525@kahikatea.snap.net.nz> <1131630516.7443.6.camel@linux.site> X-SW-Source: 2005-11/txt/msg00172.txt.bz2 Daniel Berlin writes: > > GDB is GNU gdb Red Hat Linux (6.1post-1.20040607.43rh) but I get the same > > result with GDB from the CVS repository, which worked with an earlier GCC > > (3.2 something on Mandrake 9), so I'm pretty sure that the problem > > doesn't lie with GDB. > If you run readelf -wm on the executable, does it display your macro > somewhere? It has the line: DW_MACINFO_define - lineno : 6 macro : NCR 4 > If so, then we've put it in the debug info, and that's all we can do :) Should that guarantee GDB will find it? Does GDB just use readelf or the same libraries? I presumed this would be a known problem, thats why I didn't mail it to gcc-bugs. Of course, I could be doing something stupid, but I'm not really doing anything - just using Fedora Core 3. Nick