From: "Brad M. Garcia" <bgarcia@fore.com>
To: anand@kolmogorov.cog.jhu.edu
Cc: egcs@cygnus.com
Subject: Re: How to debug code that uses the STL library?
Date: Wed, 18 Feb 1998 04:16:00 -0000 [thread overview]
Message-ID: <Pine.LNX.3.96.980218071156.23568A-100000@spud.eng.fore.com> (raw)
Anand Raman (anand@hebb.cog.jhu.edu) wrote:
> Is there a egcs compiler option that says don't compile debug info
> into files included from this one?
Compile your code with "-fno_implicit_templates -g".
In another file, do explicit template instantiations for the
templates that you require (if you don't know how to do that,
get a c++ book), and compile it _without_ the two flags shown
above. Link all files together and you're done.
Brad Garcia
___/ __ / __ / ___/ "Being the Linux of digital media
__/ / / / _/ __/ would be a very good life."
_/ ____/ _/ _| ____/ - Jean-Louis Gassee, CEO of Be, Inc.
next reply other threads:[~1998-02-18 4:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-02-18 4:16 Brad M. Garcia [this message]
-- strict thread matches above, loose matches on Subject: below --
1998-02-17 14:37 Anand Raman
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=Pine.LNX.3.96.980218071156.23568A-100000@spud.eng.fore.com \
--to=bgarcia@fore.com \
--cc=anand@kolmogorov.cog.jhu.edu \
--cc=egcs@cygnus.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).