From: Andrew Cagney <ac131313@cygnus.com>
To: debashis mahata <debashis.mahata@wipro.com>
Cc: gdb@sources.redhat.com, Elena Zannoni <ezannoni@cygnus.com>
Subject: Re: Double ';' problem in stabs
Date: Thu, 03 Jan 2002 20:22:00 -0000 [thread overview]
Message-ID: <3C352E10.4030009@cygnus.com> (raw)
In-Reply-To: <001601c18f83$e123ebc0$73b17fc0@8420044-mahatad.wipro.com>
> Questions:
> 1. Is it anywhere documented that the last ';' (the second one) should
> be present?
> 2. If not, is it a bug (the assumption that last ';' should
> be persent) in Gdb, which requires a fix?
> 3. In case a fix is required what will be the long term strategy?
I'd treat it as a GDB bug - even if someone could find a spec indicating
that Sun's compiler is producing bad STABS, GDB should still be handling
them. Could I suggest at least filing a bug report at
http://sources.redhat.com/gdb/bugs/
enjoy,
Andrew
next prev parent reply other threads:[~2002-01-04 4:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-28 1:44 debashis mahata
2002-01-03 20:22 ` Andrew Cagney [this message]
2002-01-04 11:45 ` Elena Zannoni
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=3C352E10.4030009@cygnus.com \
--to=ac131313@cygnus.com \
--cc=debashis.mahata@wipro.com \
--cc=ezannoni@cygnus.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