public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Gene.Thomas@eServGlobal.com
To: gcc-gnats@gcc.gnu.org
Subject: c++/10599: -O2 with exception in shared libraries with -O2 optimisation on HP-UX 11 g++ cause Segmentation fault
Date: Fri, 02 May 2003 06:56:00 -0000 [thread overview]
Message-ID: <20030502065005.22270.qmail@sources.redhat.com> (raw)
>Number: 10599
>Category: c++
>Synopsis: -O2 with exception in shared libraries with -O2 optimisation on HP-UX 11 g++ cause Segmentation fault
>Confidential: no
>Severity: serious
>Priority: medium
>Responsible: unassigned
>State: open
>Class: wrong-code
>Submitter-Id: net
>Arrival-Date: Fri May 02 06:56:00 UTC 2003
>Closed-Date:
>Last-Modified:
>Originator: Gene Thomas
>Release: gcc version 3.2
>Organization:
>Environment:
> uname -a
HP-UX hp14 B.11.00 A 9000/785 2013266428 two-user license
> gcc -v
Reading specs from /opt/gcc-3.2/lib/gcc-lib/hppa2.0w-hp-hpux11.00/3.2/specs
Configured with: ./configure --prefix=/opt/gcc-3.2 --enable-shared --with-gnu-as --with-as=/opt/binutils/bin/as --enable-libgcj : (reconfigured) ./configure --prefix=/opt/gcc-3.2 --enable-shared --with-gnu-as --with-as=/opt/binutils/bin/as
Thread model: single
gcc version 3.2
>Description:
When compiling the attached program on HP-UX 11.0 (works on Linux), and an exception thrown from a shared library and caught in the host application, when optimisation is on (-O2) the program core dumps when one attempts to look into the caught exception (printing .what() or looking at the typeid() infomation.
>How-To-Repeat:
ungzip and untar the attached source, gmake and run ./exceptionProblem.
This core dumps, see source for simple (as possible) test program.
>Fix:
>Release-Note:
>Audit-Trail:
>Unformatted:
----gnatsweb-attachment----
Content-Type: application/x-gzip-compressed; name="soure.tar.gz"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="soure.tar.gz"
H4sICCUUsj4AA3NvdXJlLnRhcgDtWFtr2zAU7mv0Kw4pDIcubpwr2KUPG3sY7FLoDxiOrMSmthQs
ZW0Z+e/TxXKcxFkG64UyfQ91de7nOPpyWvKAyUpkjN6UbJ6Twsf47KkxkJhNp/IZBNPpuPHUCIaD
4Zk0mIzHg9lkFCj9NAhmZ4Mnr6QFay7iUqZcipQVMT9qd0pfNVM/3wjQeUZxvk4IXBH7UbhuCMXj
imR0wZqyjHFRkri4RlthN8/mfpp2EewBZVRAEWfU68EvrdU/RPlYHWuRwuWlSEt2DzJaGN5mxSon
n2xZXi86sOMiCcNyTUVWkB+kLFnpdR+6DcNtaBPysZizHLg3bNhojY63zcWlXhtsAMcCp+BhRrkw
CetJwTvSa7ShlViWAVdX0MXxepmKELrqpOeYeKTn07ggchZSZmLRJI9ORLhPYxuH+Opw1L8kYl1S
6AfR7mzrLnzf33kPh0nX1KQFzgoi0owuuyeSDY1os41qIrK1MG0w9R4FSYDd7cfaoNe+Af831LV9
BsrfwQn+H4wG4y3/B5r/R6Px1PH/C6CFwRFSFMVXMSaKGiVboJ8sS2CPIS2VWjr5G+q2Nq28bQI2
KdgSuXE61Cv6cAzyTzAv/Xlz6Ps/mx3d/4J6/wskGbj7/5JorHXcbnUNkUjMrnPdQgo4jzmvbqU6
A6hVj0ZotZ7nGQ6VxGg9pchoD0KzO1BPHRRtbCqvJRHf5FJjdiy7UFX7BY0qQ00aski5koBgt/oX
b7t/NdSmE+DcLiuyULl30Gg3Mue+tDTktEGbaLenmmkgBNNSC23p7Dqq5UP9iKCeQrUT7bNXZZ4Z
+3o0srZdVvwQJzZ0Fy6svb/tv/feevJq2DakHsxmm1xNuXohR0ZdFW/81Dz+zPyRY9+3jq/xHVlk
OXnOHCf4fzAdTWr+nwQjzf+zkeP/lwAie/8AChW9q62A57Cv8xnqLC8uWuTQ/wI+9HP11dBnBwao
c5DHZ+FhHIzBLCQmTx+3mrQkkJUh5cl0+Qdxvg+hv7j5/BH6PI1L+YdoH1s7GUw7onNlhgDV7YeV
orNUZtZxscqML6tcjXEHnccl4NJK4spZfqOQmIYh6pSFdG4bXdMjryZvnF/7w+Hg4ODg4ODg4ODg
4ODg4ODg4ODwpvEb/6wjigAoAAA=
reply other threads:[~2003-05-02 6:56 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20030502065005.22270.qmail@sources.redhat.com \
--to=gene.thomas@eservglobal.com \
--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).