From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 26602 invoked by alias); 28 Sep 2002 16:37:59 -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 26594 invoked from network); 28 Sep 2002 16:37:58 -0000 Received: from unknown (HELO hal.astr.lu.lv) (195.13.134.67) by sources.redhat.com with SMTP; 28 Sep 2002 16:37:58 -0000 Received: from laser3.geodeet.fgi.fi (IDENT:1000@laser3.metsahovi.fgi.fi [130.233.244.100]) by hal.astr.lu.lv (8.12.6/8.12.4) with ESMTP id g8SGZbbc001105; Sat, 28 Sep 2002 19:35:37 +0300 From: Andris Reply-To: pavenis@lanet.lv Organization: Pavenis To: Andrew Cagney Subject: Re: Internal GDB errors with current GDB snapshots and -gdwarf-23 Date: Sat, 28 Sep 2002 09:37:00 -0000 User-Agent: KMail/1.4.7 Cc: djgpp-workers@delorie.com, gdb@sources.redhat.com References: <3D6E31F2.25704.9E195D@localhost> <3D89F4C2.90809@ges.redhat.com> In-Reply-To: <3D89F4C2.90809@ges.redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Message-Id: <200209281640.59537.pavenis@lanet.lv> X-SW-Source: 2002-09/txt/msg00497.txt.bz2 On Thursday 19 September 2002 19:01, Andrew Cagney wrote: > Has anyone had a chance to look at this? > > Andrew Tried today (with GDB-5.2.90_20020927) and reported results to bug report g= db/726.=20 Currently I don't see other way for DJGPP as extremly ugly workaround (perh= aps=20 no need to get it in official GDB sources): --- gdb+dejagnu-5.2.90_20020927/gdb/macrotab.c~1 2002-07-29 22:55:26.000000= 000 +0000 +++ gdb+dejagnu-5.2.90_20020927/gdb/macrotab.c 2002-09-28 16:24:58.00000000= 0 +0000 @@ -272,7 +272,14 @@ { /* They can't both be from #included files. Then we shouldn't have walked up this far. */ + /* FIXME: Workaround for GCC bug: it misinterprets include from line= 1 + as from line2 when -imacros is used (in this case both lines + could be 2) AP, 2002/09/28 */ +#if defined(__DJGPP__) + gdb_assert (! included1 || ! included2 || line1=3D=3D2); +#else gdb_assert (! included1 || ! included2); +#endif =20 /* Any #included position comes after a non-#included position with the same line number in the #including file. */ Andris