public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: bkoz@gcc.gnu.org
To: bkoz@gcc.gnu.org, chris@tti-telecom.com, gcc-bugs@gcc.gnu.org,
	gcc-prs@gcc.gnu.org, nobody@gcc.gnu.org
Subject: Re: libstdc++/5166: Segfault when using global std::string from dlopen
Date: Fri, 05 Apr 2002 11:14:00 -0000	[thread overview]
Message-ID: <20020405191402.30228.qmail@sources.redhat.com> (raw)

Synopsis: Segfault when using global std::string from dlopen

Responsible-Changed-From-To: unassigned->bkoz
Responsible-Changed-By: bkoz
Responsible-Changed-When: Fri Apr  5 11:14:02 2002
Responsible-Changed-Why:
    Mine.
State-Changed-From-To: open->feedback
State-Changed-By: bkoz
State-Changed-When: Fri Apr  5 11:14:02 2002
State-Changed-Why:
    See libstdc++/6062. I'd appreciate it if you'd try this with the gcc-3.1 toolchain. 
    
    Building with a current toolchain on linux:
    c++ -rdynamic -g -fPIC -Wall -shared mydll.cc -o lib5166.so 
    c++ -rdynamic -g -fPIC -Wall main.cc -L. -l5166 -ldl -o test.exe
    
    Gives:
    
    %./test.exe 
    hello
    hello
    
    
    Thoughts? This is probably what you were expecting on HPUX. 
    
    I think this is either a gcc-on-HPUX specific problem, or a problem with the HPUX dynamic linker. Thoughts on how to proceed?
    
    -benjamin

http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=5166


             reply	other threads:[~2002-04-05 19:14 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-05 11:14 bkoz [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-04-08 14:56 Christoph Bugel
2002-04-05 11:57 bkoz
2001-12-20  8:36 Christoph Bugel

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=20020405191402.30228.qmail@sources.redhat.com \
    --to=bkoz@gcc.gnu.org \
    --cc=chris@tti-telecom.com \
    --cc=gcc-bugs@gcc.gnu.org \
    --cc=gcc-gnats@gcc.gnu.org \
    --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).