From: Mark Geisert <mark@maxrnd.com>
To: cygwin@cygwin.com
Subject: Re: Cygwin 2.6.0 Fork issue
Date: Thu, 05 Jan 2017 10:17:00 -0000 [thread overview]
Message-ID: <586E1D31.9080907@maxrnd.com> (raw)
In-Reply-To: <CAPCR6Q0p4dOqYBxeF4BohZeEq=GjctdbU4wvFxY7=5eUzyPJwQ@mail.gmail.com>
Rashi Singhal wrote:
> Hi ,
> Thanks for information provided.
>
> I tried putting cygwin/ bin path in first place in environment
> variables. But result remain same.
OK.
> Yes all other DLL's getting loaded are either pervasive dll or windows
> native dll.
You might be missing the essential point here. Windows-native DLLs that make
use of the Microsoft C runtime are not compatible with Cygwin. They will not
work properly. If Actian Pervasive separately supplies their code as Cygwin
DLLs, you must use those.
> I have doubt ,.Is there any compilation variable or cygwin varaible
> set for autoloading all dll's
Not sure why you're asking this.
> As in same windows 2012 system this extra DLL's are not getting loaded
> with previous versions of cywin and Fork is working there.
You're saying that on this same computer, running Win 2012, this sample code ran
properly under a previous version of Cygwin? Which version was that?
> I have downloaded the source also, I check some varibel there if you can help.
Which source have you downloaded? Whose source?
> Looks like program just hangs child process after open call and never
> comes back.
>
> Please suggest what I can check .
Your sample program is getting exceptions (i.e., is faulting) even before it
fork()s the child process. The child is faulting the same way. This looks
pretty much like your sample program was built with incorrect assumptions.
You can try posting the compilation (and linking) command(s) that you used to
build your btrsamp.exe program. Maybe there's something obvious there that
somebody here can see. We can't help you debug your program though, and you
can't mix Windows-native DLLs that use Microsoft C runtime with Cygwin code.
..mark
--
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 prev parent reply other threads:[~2017-01-05 10:17 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-03 8:53 Rashi Singhal
2017-01-05 4:04 ` Rashi Singhal
2017-01-05 10:17 ` Mark Geisert [this message]
2017-01-06 2:58 ` Rashi Singhal
[not found] <586F5B5F.1070407@maxrnd.com>
2017-01-06 9:05 ` Mark Geisert
2017-01-06 20:34 ` René Berber
-- strict thread matches above, loose matches on Subject: below --
2017-01-03 11:17 Mark Geisert
2016-12-08 5:37 Rashi Singhal
2016-12-08 7:17 ` Brian Inglis
2016-12-16 9:28 ` Rashi Singhal
2016-12-30 8:25 ` Rashi Singhal
2016-12-30 19:25 ` Eliot Moss
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=586E1D31.9080907@maxrnd.com \
--to=mark@maxrnd.com \
--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).