From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 977 invoked by alias); 15 Jan 2009 21:40:25 -0000 Received: (qmail 961 invoked by alias); 15 Jan 2009 21:40:25 -0000 Date: Thu, 15 Jan 2009 21:40:00 -0000 Message-ID: <20090115214025.960.qmail@sourceware.org> From: "drow at false dot org" To: gdb-prs@sourceware.org In-Reply-To: <20090115210626.9748.rearnsha@gcc.gnu.org> References: <20090115210626.9748.rearnsha@gcc.gnu.org> Reply-To: sourceware-bugzilla@sourceware.org Subject: [Bug macros/9748] macros containing __extension__ won't run X-Bugzilla-Reason: CC Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-prs-owner@sourceware.org X-SW-Source: 2009-q1/txt/msg00074.txt.bz2 ------- Additional Comments From drow at false dot org 2009-01-15 21:40 ------- Subject: Re: macros containing __extension__ won't run On Thu, Jan 15, 2009 at 09:30:06PM -0000, pedro at codesourcery dot com wrote: > I current gdb mainline, you could try defining __extension__ to empty: > > (gdb) macro define __extension__ > > ("macro define" was stubbed in yearlier versions of gdb, it > has only recently been implemented) > > I guess you'd need to do the same for __FILE__, __LINE__, etc, but I > think you'll trip on __typeof. Also on statement expressions, which is what the __extension__ marker is for in the first place :-) I don't think statement expressions are likely to be implemented in GDB. It currently has only a C expression parser, with no support for statements etc. -- http://sourceware.org/bugzilla/show_bug.cgi?id=9748 ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.