Internal GDB errors with current GDB snapshots and -gdwarf-23
Andris
pavenis@lanet.lv
Sat Sep 28 09:37:00 GMT 2002
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 gdb/726.
Currently I don't see other way for DJGPP as extremly ugly workaround (perhaps
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.000000000 +0000
+++ gdb+dejagnu-5.2.90_20020927/gdb/macrotab.c 2002-09-28 16:24:58.000000000 +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==2);
+#else
gdb_assert (! included1 || ! included2);
+#endif
/* Any #included position comes after a non-#included position
with the same line number in the #including file. */
Andris
More information about the Gdb
mailing list