public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: hans.utz@informatik.uni-ulm.de
To: gcc-gnats@gcc.gnu.org
Subject: c++/8847: dynamic_cast segfaults with shared lib
Date: Fri, 06 Dec 2002 08:56:00 -0000	[thread overview]
Message-ID: <20021206165235.22884.qmail@sources.redhat.com> (raw)


>Number:         8847
>Category:       c++
>Synopsis:       dynamic_cast segfaults with shared lib
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Fri Dec 06 08:56:01 PST 2002
>Closed-Date:
>Last-Modified:
>Originator:     Hans Utz
>Release:        3.2.1
>Organization:
>Environment:
Linux SuSE 7.3 box (Athlon)
gcc -v:
Reading specs from /data1/hutz/3.2/gcc/lib/gcc-lib/i686-pc-linux-gnu/3.2.1/specs
Configured with: ../gcc-3.2.1/configure --prefix=/data1/hutz/3.2/gcc
Thread model: posix
gcc version 3.2.1
>Description:
When compiling the attached minimal test program linking it
with libGLU.so.1.3 and libGL, the execution fails with a 
segmentation fault on the dynamic_cast statement. - 
When compiling with just libGL or no library everything 
works fine.

g++ Test.cc              # okay
g++ Test.cc -lGL         # okay
g++ Test.cc -lGLU -lGL   # segfault

I know that it is not a good test case, as it depends on
some library on some distribution, but maybe it's a
starting point for a better test case. - As I don't know
how to find out about what's going wrong when linking with 
libGLU I'm stuck.

Thanks,
Hans 
>How-To-Repeat:

>Fix:

>Release-Note:
>Audit-Trail:
>Unformatted:
----gnatsweb-attachment----
Content-Type: application/octet-stream; name="Test.cc"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="Test.cc"

c3RydWN0IEZvbwp7CiAgdmlydHVhbCB+Rm9vKCk7Cn07CgpGb286On5Gb28oKSB7fQoKc3RydWN0
IEJhciA6IHB1YmxpYyBGb28KewogIHZpcnR1YWwgfkJhcigpOwp9OwoKQmFyOjp+QmFyKCkge30K
CmludCBtYWluKGludCwgY2hhciAqKikKewogIEZvbyAqIGZvbyA9IG5ldyBCYXIoKTsKICBCYXIg
KiBiYXIgPSBkeW5hbWljX2Nhc3Q8QmFyICo+KGZvbyk7CgogIHJldHVybiAwOwp9Cg==


             reply	other threads:[~2002-12-06 16:56 UTC|newest]

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

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=20021206165235.22884.qmail@sources.redhat.com \
    --to=hans.utz@informatik.uni-ulm.de \
    --cc=gcc-gnats@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).