public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dje at watson dot ibm dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/13878] Uncaught exception on AIX with shared libraries
Date: Sun, 01 Feb 2004 02:52:00 -0000 [thread overview]
Message-ID: <20040201025235.14983.qmail@sources.redhat.com> (raw)
In-Reply-To: <20040127083113.13878.joerg.richter@pdv-fs.de>
------- Additional Comments From dje at watson dot ibm dot com 2004-02-01 02:52 -------
Subject: Re: Uncaught exception on AIX with shared libraries
I think this bug is related to or a duplicate of PR 13391.
I do not understand the analysis in the bug report mentioning
overlapping FDE ranges. AIX's memory layout is more complicated than most
other systems, but it still is a flat, linear address space. Is this
trying to say that shared objects re-export symbols in other shared
objects, so the FDE and address actually corresponds to another shared
object? Or is it saying that some ranges represent the end of the module
to the top of memory when, in fact, another shared object could be in that
higher address range?
If the analysis could give some examples of symbols with
overlapping FDE ranges, that would help.
David
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=13878
next prev parent reply other threads:[~2004-02-01 2:52 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-27 8:31 [Bug c++/13878] New: " joerg dot richter at pdv-fs dot de
2004-01-31 0:43 ` [Bug c++/13878] " dhazeghi at yahoo dot com
2004-02-01 2:52 ` dje at watson dot ibm dot com [this message]
2004-02-01 10:26 ` joerg dot richter at pdv-fs dot de
2004-02-21 19:12 ` greed at pobox dot com
2004-03-01 21:01 ` smethells at llnl dot gov
2004-03-03 20:52 ` ajd at gentrack dot com
2004-03-03 22:50 ` dje at gcc dot gnu dot org
2004-03-03 22:51 ` dje at gcc dot gnu dot org
2004-03-03 22:54 ` dje at watson dot ibm dot com
2004-03-06 20:55 ` dje at gcc dot gnu dot org
2004-03-06 23:31 ` pinskia at gcc dot gnu dot org
2004-03-07 22:37 ` dje at gcc dot gnu dot org
2005-05-31 12:54 ` nagaraj_hayyal at satyam dot com
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=20040201025235.14983.qmail@sources.redhat.com \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@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).