From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 25600 invoked by alias); 11 Nov 2005 03:43:37 -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 25586 invoked by uid 22791); 11 Nov 2005 03:43:35 -0000 Received: from fencepost.gnu.org (HELO fencepost.gnu.org) (199.232.76.164) by sourceware.org (qpsmtpd/0.30-dev) with ESMTP; Fri, 11 Nov 2005 03:43:35 +0000 Received: from monty-python.gnu.org ([199.232.76.173]) by fencepost.gnu.org with esmtp (Exim 4.34) id 1EaPp7-0003vP-Da for gcc-help@gnu.org; Thu, 10 Nov 2005 22:43:33 -0500 Received: from Debian-exim by monty-python.gnu.org with spam-scanned (Exim 4.34) id 1EaPp7-0008At-Ek for gcc-help@gnu.org; Thu, 10 Nov 2005 22:43:33 -0500 Received: from [68.164.203.246] (helo=dberlin.org) by monty-python.gnu.org with esmtp (SSL 3.0:RSA_3DES_EDE_CBC_SHA:24) (Exim 4.34) id 1EaPp7-0008Ap-5w for gcc-help@gnu.org; Thu, 10 Nov 2005 22:43:33 -0500 Received: from [127.0.0.1] (HELO localhost) by dberlin.org (CommuniGate Pro SMTP 5.0c7) with ESMTP id 8269637; Thu, 10 Nov 2005 22:43:31 -0500 Subject: Re: Macro expansion: GCC 3.4.4 From: Daniel Berlin To: Nick Roberts Cc: John Love-Jensen , gcc-help@gnu.org In-Reply-To: <17267.39863.36467.881393@kahikatea.snap.net.nz> References: <17265.25812.936653.920077@kahikatea.snap.net.nz> <17266.29709.941044.86525@kahikatea.snap.net.nz> <1131630516.7443.6.camel@linux.site> <17267.39863.36467.881393@kahikatea.snap.net.nz> Content-Type: text/plain Date: Fri, 11 Nov 2005 03:43:00 -0000 Message-Id: <1131680618.7465.3.camel@linux.site> Mime-Version: 1.0 Content-Transfer-Encoding: 7bit X-SW-Source: 2005-11/txt/msg00174.txt.bz2 On Fri, 2005-11-11 at 08:12 +1300, Nick Roberts wrote: > 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 and in gdb, if you use "macro expand NCR", does it work? > > > 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? It doesn't, unfortunately, so it doesn't guarantee GDB is processing the macro info right. But it does mean we are putting it in the debug info. It's also possible the file or line number is being set wrong, etc. But you'd need to debug gdb to see it. > > 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