From: Ziqiang Tang <ztang@guitar.lcs.mit.edu>
To: gcc-help@gcc.gnu.org
Subject: libstd++/gcc question...
Date: Sat, 01 Apr 2000 00:00:00 -0000 [thread overview]
Message-ID: <200002292212.RAA16353@guitar.lcs.mit.edu> (raw)
Message-ID: <20000401000000.DvsJYPiEfeyP10u4BSQQAMCSQbeoaRkH3EXR5Cj30Ss@z> (raw)
Hi there,
I've been trying to build a clean distribution of Jikes, the IBM Java
compiler. When compiled on a new distribution of Dell-bundled RH6.1, the
executable worked fine. When compiled on my old version of RH5.2 with
these versions:
Kernel modules 2.1.85
Gnu C 2.95.2
Binutils 2.9.4.0.6
Linux C Library 2.1.2
Dynamic linker ldd (GNU libc) 2.1.2
Linux C++ Library 2.8.1
Procps 2.0.6
Mount 2.10f
Net-tools Utilities
Kbd 0.94
Sh-utils 1.16
... the binary would segfault upon exit from the program. After looking
at it through ltrace/ldd, it became clear that the version
compiled/working cleanly is linking to libstdc++-libc6.1-1.so.2, and using
__builtin_new(8, 0x401611b4, 0xbffffd44, 1, 0xbffffd18) = 0x082d1d00
__builtin_vec_new(6, 0xbffffd44, 1, 0x082d1d00, 8192) = 0x082d1d10
... etc for memory management.
The *broken* version on my machine (as shown above) is not linking to
libstdc++ and using malloc/free, with the segfault coming as a result of
multiple free-ing of the same memory location.
At first this was because libstdc++ wasn't avilable on my machine, but
even after adding the RPMs the same problem persisted... Is there
something I have to do to get GCC to recognize that it should use
libstdc++ as a standardlib when linking?
The RPM packages on my machine for libstdc++ include:
libstdc++-compat-2.95.2-3
libstdc++-2.95.2-3
libstdc++-devel-2.95.2-3
Thanks for any help.
next reply other threads:[~2000-04-01 0:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-02-29 14:11 Ziqiang Tang [this message]
2000-04-01 0:00 ` Ziqiang Tang
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=200002292212.RAA16353@guitar.lcs.mit.edu \
--to=ztang@guitar.lcs.mit.edu \
--cc=gcc-help@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).