From: Chris Faylor <cgf@cygnus.com>
To: cygwin@sources.redhat.com
Subject: Re: problem with dynamic_cast
Date: Tue, 12 Sep 2000 07:07:00 -0000 [thread overview]
Message-ID: <20000912100616.B32019@cygnus.com> (raw)
In-Reply-To: <7767-Tue12Sep2000145500+0100-starksb@ebi.ac.uk>
On Tue, Sep 12, 2000 at 02:55:00PM +0100, David Starks-Browning wrote:
>On Friday 8 Sep 00, Chris Faylor writes:
>> On Fri, Sep 08, 2000 at 12:46:31PM -0400, Chris Faylor wrote:
>> >On Fri, Sep 08, 2000 at 10:18:42AM -0400, Fleischer, Karsten (K.) wrote:
>> >>How about including the stub libraries in the distribution, rather than the
>> >>symlinks?
>> >
>> >The reason for the symlinks is that some packages search libc.a and libm.a
>> >for symbols.
>> >
>> >If linking libc.a twice causes problems, then it *is* a bug in either gcc or
>> >ld.
>> >
>> >Mumit had vowed once to fix this problem but then he disappeared...
>>
>> Ok, I looked into this. It is a linker problem. Specifying -lm or -lc on
>> the command line causes ld to put symbols into the import section in improperly
>> sorted order.
>>
>> This confuses the Windows "dynamic loader" (and I use the term loosely) so that
>> certain function calls (namely strcmp and strlen) are not resolved. So when
>> a function in libgcc needs to call strcmp it ends up jumping into unallocated
>> memory, causing a SIGSEGV.
>>
>> That's the analysis. I have no idea how to fix this, but I've sent some details
>> to DJ in the hopes that he'll be able to do something about this.
>
>Would it be helpful if I put this in the FAQ?
>(Under "Known Problems in the Current Net Release".)
Yes. "We" (this is the royal we) are working on the problem in the meantime.
cgf
--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com
next prev parent reply other threads:[~2000-09-12 7:07 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-09-08 7:19 Fleischer, Karsten (K.)
2000-09-08 9:47 ` Chris Faylor
2000-09-08 20:01 ` Chris Faylor
2000-09-12 6:55 ` David Starks-Browning
2000-09-12 7:07 ` Chris Faylor [this message]
2000-10-04 15:20 ` Chris Faylor
-- strict thread matches above, loose matches on Subject: below --
2000-09-08 7:21 Bernard Dautrevaux
2000-09-08 7:10 Earnie Boyd
2000-09-08 8:04 ` Kris Thielemans
2000-09-08 6:13 Fleischer, Karsten (K.)
[not found] <B0016139757@mzdy10.allegro.net>
2000-09-08 5:56 ` Kris Thielemans
2000-09-08 4:58 Fleischer, Karsten (K.)
2000-09-08 6:56 ` Larry Hall (RFK Partners, Inc)
2000-09-08 7:04 ` Kris Thielemans
2000-09-08 7:16 ` Larry Hall (RFK Partners, Inc)
2000-09-07 8:52 Kris Thielemans
2000-09-07 9:02 ` Chris Faylor
2000-09-08 4:48 ` Kris Thielemans
2000-08-31 8:01 Kris Thielemans
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=20000912100616.B32019@cygnus.com \
--to=cgf@cygnus.com \
--cc=cygwin@sources.redhat.com \
/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).