public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Craig Rodrigues <rodrigc@mediaone.net>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: c++/3524: Source can not be comiled using option -gdwarf
Date: Fri, 14 Dec 2001 13:06:00 -0000 [thread overview]
Message-ID: <20011214210601.19847.qmail@sources.redhat.com> (raw)
The following reply was made to PR c++/3524; it has been noted by GNATS.
From: Craig Rodrigues <rodrigc@mediaone.net>
To: gcc-gnats@gcc.gnu.org
Cc:
Subject: Re: c++/3524: Source can not be comiled using option -gdwarf
Date: Fri, 14 Dec 2001 15:55:29 -0500
----- Forwarded message from Bailing Li <Bailing.Li@noaa.gov> -----
Delivered-To: rodrigc@gcc.gnu.org
From: "Bailing Li" <Bailing.Li@noaa.gov>
To: rodrigc@gcc.gnu.org
Date: Fri, 14 Dec 2001 19:40:02 GMT
X-Mailer: Netscape Webmail
Subject: Re: c++/3524: Source can not be comiled using option -gdwarf
X-Accept-Language: en
Not really. Using makes the code buildable, but it crashed in my pgdbg
debug which is dwarf based.
What's the difference between -gdwarf and -gdwarf-2?
Thanks any information,
Bailing
----- Original Message -----
From: rodrigc@gcc.gnu.org
Date: Friday, December 14, 2001 7:17 pm
Subject: Re: c++/3524: Source can not be comiled using option -gdwarf
> Synopsis: Source can not be comiled using option -gdwarf
>
> State-Changed-From-To: open->analyzed
> State-Changed-By: rodrigc
> State-Changed-When: Fri Dec 14 11:17:23 2001
> State-Changed-Why:
> Reproduced in gcc 3.1 and gcc 3.0 branch.
>
> Is using -gdwarf-2 an acceptable workaround?
>
> http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-
> trail&pr=3524&database=gcc
----- End forwarded message -----
--
Craig Rodrigues
http://www.gis.net/~craigr
rodrigc@mediaone.net
next reply other threads:[~2001-12-14 21:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-14 13:06 Craig Rodrigues [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-12-14 11:26 rodrigc
2001-12-14 11:17 rodrigc
2001-07-01 23:36 axel.geller
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=20011214210601.19847.qmail@sources.redhat.com \
--to=rodrigc@mediaone.net \
--cc=gcc-prs@gcc.gnu.org \
--cc=nobody@gcc.gnu.org \
/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).