public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: <christoph.wiedemann@daimlerchrysler.com>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: c++/8847: dynamic_cast segfaults with shared lib
Date: Mon, 27 Jan 2003 13:06:00 -0000	[thread overview]
Message-ID: <20030127130601.29287.qmail@sources.redhat.com> (raw)

The following reply was made to PR c++/8847; it has been noted by GNATS.

From: <christoph.wiedemann@daimlerchrysler.com>
To: <nobody@gcc.gnu.org>, <gcc-bugs@gcc.gnu.org>,
        <hans.utz@informatik.uni-ulm.de>, <gcc-prs@gcc.gnu.org>,
        <gcc-gnats@gcc.gnu.org>, <himself@markus-hillebrand.de>
Cc:  
Subject: Re: c++/8847: dynamic_cast segfaults with shared lib
Date: Mon, 27 Jan 2003 14:00:23 +0100

  =20
 http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=3Dview%20audit-trail&databas=
 e=3Dgcc&pr=3D88
 47
 
 Hi,
 
 i had the same problem with linking against libGLU.so.=20
 It seems to be that dynamic_cast is internally using the symbol __dynam=
 ic_cast,=20
 which is exported by libGLU:
 
 >nm /usr/lib/libGLU.so | grep dynamic_cast
 >0007b1d4  T  __dynamic_cast
 
 but also by libstdc++:
 
 >nm /usr/local/lib/libstdc++.so | grep dynamic_cast
 >00050a00  T  __dynamic_cast
 
 In my case, it is enough to export the environment variable LD_PRELOAD =
 to the=20
 /usr/local/lib/libstdc++.so, or to pass the linker flag -lstdc++ as the=
  _first_=20
 -l option.
 
 Kind Regards,
 -----------------------------------------------------------------------=
 ---------
 ----- Christoph Wiedemann=20
 DaimlerChrysler AG, Research Center Ulm=20
 P.O. Box 2360, 89013 Ulm, Germany=20
 
 Phone: +49 731 505 4123=20
 e-mail: christoph.wiedemann@daimlerchrysler.com=20
 -----------------------------------------------------------------------=
 ---------
 ----- =


             reply	other threads:[~2003-01-27 13:06 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-27 13:06 christoph.wiedemann [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-01-27 15:54 bangerth
2003-01-18  0:36 Markus Hillebrand
2002-12-09 13:46 Reinier.Bezuidenhout
2002-12-06  9:26 Hans Utz
2002-12-06  9:13 bangerth
2002-12-06  8:56 hans.utz

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=20030127130601.29287.qmail@sources.redhat.com \
    --to=christoph.wiedemann@daimlerchrysler.com \
    --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).