From: Elena Zannoni <ezannoni@redhat.com>
To: Michael Elizabeth Chastain <mec@shout.net>
Cc: gdb@sources.redhat.com
Subject: Re: gdb/1180: gcc bug or gdb bug?
Date: Wed, 23 Apr 2003 02:16:00 -0000 [thread overview]
Message-ID: <16037.63660.347124.981160@localhost.redhat.com> (raw)
In-Reply-To: <200304191548.h3JFmmJG017080@duracef.shout.net>
Michael Elizabeth Chastain writes:
> Hi guys,
>
> Can I get someone to look at gdb/1180 and say whether it's a
> gcc bug or a gdb bug?
>
> gcc changed its debugging output and gdb doesn't like the new output.
> I need to decide whether to file a PR against gcc about it.
>
> Michael C
> Whiney QA guy
This seems like a gcc debuginfo problem to me. There is a lexical
block for the innermost block but not for the middle one.
elena
next prev parent reply other threads:[~2003-04-23 2:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-19 15:48 Michael Elizabeth Chastain
2003-04-23 2:16 ` Elena Zannoni [this message]
2003-04-23 3:07 ` Daniel Jacobowitz
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=16037.63660.347124.981160@localhost.redhat.com \
--to=ezannoni@redhat.com \
--cc=gdb@sources.redhat.com \
--cc=mec@shout.net \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).