From: Andris <pavenis@lanet.lv>
To: Andrew Cagney <ac131313@ges.redhat.com>
Cc: djgpp-workers@delorie.com, gdb@sources.redhat.com
Subject: Re: Internal GDB errors with current GDB snapshots and -gdwarf-23
Date: Sat, 28 Sep 2002 09:37:00 -0000 [thread overview]
Message-ID: <200209281640.59537.pavenis@lanet.lv> (raw)
In-Reply-To: <3D89F4C2.90809@ges.redhat.com>
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
prev parent reply other threads:[~2002-09-28 16:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-29 4:51 pavenis
2002-09-19 10:00 ` Andrew Cagney
2002-09-22 16:08 ` Jim Blandy
2002-09-28 9:37 ` Andris [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200209281640.59537.pavenis@lanet.lv \
--to=pavenis@lanet.lv \
--cc=ac131313@ges.redhat.com \
--cc=djgpp-workers@delorie.com \
--cc=gdb@sources.redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox