public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: "Ralf W. Grosse-Kunstleve" <rwgk@yahoo.com> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: other/6602: GCC/Linux shared lib + EH bug example Date: Wed, 08 May 2002 11:26:00 -0000 [thread overview] Message-ID: <20020508182601.23896.qmail@sources.redhat.com> (raw) The following reply was made to PR other/6602; it has been noted by GNATS. From: "Ralf W. Grosse-Kunstleve" <rwgk@yahoo.com> To: c++-sig@python.org, gcc-gnats@gcc.gnu.org Cc: loewis@informatik.hu-berlin.de Subject: Re: other/6602: GCC/Linux shared lib + EH bug example Date: Wed, 8 May 2002 11:23:02 -0700 (PDT) Martin v. Loewis wrote: > Looking at your example gcc_dl_eh: Can you please try to not define > the worker_error dtor inline? I.e. implement it in libcore.cpp > instead; I'd be curious whether this changes anything. It does not change the outcome. See attached. Thanks, Ralf % make gcc -g -c master.c gcc -o master master.o -ldl g++ -g -c ext1.cpp g++ -g -c libcore.cpp g++ -shared -Wl,-E -o libcore.so libcore.o g++ -shared -Wl,-E -o ext1.so ext1.o libcore.so g++ -g -c ext2.cpp g++ -shared -Wl,-E -o ext2.so ext2.o libcore.so ********************************************************* LD_LIBRARY_PATH=.:/usr/local_cci/gcc-3.0.4/lib master G 1 dlopen flag: RTLD_GLOBAL init_ext1 init_ext2 run1 mycore::dispatcher ext1::worker now throwing worker_error() success catching worker_error run2 mycore::dispatcher ext2::worker now throwing worker_error() success catching worker_error ********************************************************* LD_LIBRARY_PATH=.:/usr/local_cci/gcc-3.0.4/lib master G 2 dlopen flag: RTLD_GLOBAL init_ext2 init_ext1 run1 mycore::dispatcher ext1::worker now throwing worker_error() success catching worker_error run2 mycore::dispatcher ext2::worker now throwing worker_error() success catching worker_error ********************************************************* LD_LIBRARY_PATH=.:/usr/local_cci/gcc-3.0.4/lib master L 1 dlopen flag: RTLD_LOCAL init_ext1 init_ext2 run1 mycore::dispatcher ext1::worker now throwing worker_error() success catching worker_error run2 mycore::dispatcher ext2::worker now throwing worker_error() ################################# # # # FAILURE catching worker_error # # # ################################# ********************************************************* LD_LIBRARY_PATH=.:/usr/local_cci/gcc-3.0.4/lib master L 2 dlopen flag: RTLD_LOCAL init_ext2 init_ext1 run1 mycore::dispatcher ext1::worker now throwing worker_error() ################################# # # # FAILURE catching worker_error # # # ################################# run2 mycore::dispatcher ext2::worker now throwing worker_error() success catching worker_error __________________________________________________ Do You Yahoo!? Yahoo! Health - your guide to health and wellness http://health.yahoo.com
next reply other threads:[~2002-05-08 18:26 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-05-08 11:26 Ralf W. Grosse-Kunstleve [this message] -- strict thread matches above, loose matches on Subject: below -- 2002-05-09 12:16 Ralf W. Grosse-Kunstleve 2002-05-08 15:36 Ralf W. Grosse-Kunstleve 2002-05-07 22:56 Ralf W. Grosse-Kunstleve 2002-05-07 19:26 rwgk
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=20020508182601.23896.qmail@sources.redhat.com \ --to=rwgk@yahoo.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: linkBe 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).