From: "Houder" <houder@xs4all.nl>
To: cygwin@cygwin.com
Subject: Re: Core dump on 32-bit Cygwin if program calls dlopen
Date: Tue, 15 Jul 2014 13:34:00 -0000 [thread overview]
Message-ID: <5a37d9e5b16d8bf364b4a5239b02e6d3.squirrel@webmail.xs4all.nl> (raw)
>> FWIW, the problem disappears if I revert gcc-core and libgcc1 to 4.8.2-2.
> JonY, do you have a chance to have a look into this issue?
Trying to help ...
----- test program
#include <windows.h>
#include <stdio.h>
//int main (int argc, char **argv)
int main (int argc, char *argv[])
{
HMODULE m = LoadLibrary (argv[1]);
if (!m)
printf ("%s: %lu\n", argv[1], GetLastError ());
else
printf ("Success.\n");
// 15/07/2014: currently resulting in a crash on 32-bits only (gcc only)
return 0;
}
-----
The test program above fails (abort) for every cyg*.dll in /usr/bin that pulls in cyggcc_s-1.dll.
(if not, the test program exits normally)
(using the same compiler and cygwin1.dll as Ken did)
H.
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
next reply other threads:[~2014-07-15 13:34 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-15 13:34 Houder [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-07-15 14:45 Jan Nijtmans
2014-07-15 15:29 ` Corinna Vinschen
2014-07-14 23:42 Ken Brown
2014-07-15 9:03 ` Corinna Vinschen
2014-07-15 11:45 ` Ken Brown
2014-07-15 13:08 ` Corinna Vinschen
2014-07-15 13:56 ` JonY
2014-07-15 14:39 ` Corinna Vinschen
2014-07-16 7:02 ` Corinna Vinschen
2014-07-16 22:03 ` JonY
2014-07-17 7:37 ` Corinna Vinschen
2014-07-17 15:31 ` Jon TURNEY
2014-07-17 18:24 ` Corinna Vinschen
2014-07-20 22:02 ` JonY
2014-07-22 8:27 ` Corinna Vinschen
2014-07-22 13:00 ` Jon TURNEY
2014-07-22 13:20 ` Corinna Vinschen
2014-07-24 13:08 ` Kai Tietz
2014-07-24 13:45 ` Corinna Vinschen
2014-07-24 22:15 ` JonY
2014-07-25 12:37 ` Corinna Vinschen
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=5a37d9e5b16d8bf364b4a5239b02e6d3.squirrel@webmail.xs4all.nl \
--to=houder@xs4all.nl \
--cc=cygwin@cygwin.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).