From: Joe Buck <jbuck@synopsys.com>
To: cdern@pre.com (Chris Dern)
Cc: jbuck@synopsys.com, egcs@cygnus.com
Subject: Re: STL Question.
Date: Wed, 25 Feb 1998 18:56:00 -0000 [thread overview]
Message-ID: <199802260134.RAA16383@atrus.synopsys.com> (raw)
In-Reply-To: <34F4C3E2.7972514A@pre.com>
> The program dumps core, when run. If I use -frepo, it won't link correctly
> after collect2 decideds to re-compile (-fpreo), the linker complains of
> missing functions.
I suspect that the core dump is a bug in your program: putting pointers
in STL objects can be a bit tricky, as you must do your own memory
management. As for the missing functions, this could be a bug, or
it could be that the functions are actually missing (template definitions
not visible). One way to test that is to build without -frepo and
see if you are missing anything.
next prev parent reply other threads:[~1998-02-25 18:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-02-25 9:33 Chris Dern
1998-02-25 18:48 ` Joe Buck
1998-02-25 19:37 ` Chris Dern
1998-02-25 18:56 ` Joe Buck [this message]
1998-09-24 3:26 STL question Alexander Samoilov
1998-09-26 0:52 ` Alexandre Oliva
1998-09-28 9:26 ` Joe Buck
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=199802260134.RAA16383@atrus.synopsys.com \
--to=jbuck@synopsys.com \
--cc=cdern@pre.com \
--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).