From: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
To: cygwin@cygwin.com
Subject: Re: Cygwin 2.6.0 Fork issue
Date: Thu, 08 Dec 2016 07:17:00 -0000 [thread overview]
Message-ID: <2df1b680-a0f4-f7aa-292a-4dbe752e089b@SystematicSw.ab.ca> (raw)
In-Reply-To: <CAPCR6Q2e-VPw_x_S+qewHSbD=cV74eZ4oo23cdVtJxjUJvTRTw@mail.gmail.com>
On 2016-12-07 22:37, Rashi Singhal wrote:
> I am using cygwin 2.6.0 (32 bit) version with Actian Pervasive
> version 12.
> We have a program which will call fork() and in child process
> Btrieve file is getting opened.
> While using latest version of cygwin, file open call is not working
> Its not opening file nor displaying any error.
> Could you please help me on this .
With some information to go on, someone on the list may be able to
help you.
Please read the contents of the web page at the link below and
follow the instructions:
> Problem reports: http://cygwin.com/problems.html
Attach the text from cygcheck -svr, a Simple Test Case minimal source
program, which when run demonstrates the problem, and the output from
that test run, and/or the log from a gdb session, and/or the output
from strace, running the Simple Test Case minimal source program,
demonstrating the problem.
As the problem is a file open, you may also want to add the output
from running ls -l, stat, getfacl, and icacls on the file, as file
open problems often result from permissions issues, so it is also
important to run cygcheck, tests, and file info using the same
environment and credentials as when the problem occurs.
--
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada
--
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:[~2016-12-08 7:17 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-08 5:37 Rashi Singhal
2016-12-08 7:17 ` Brian Inglis [this message]
2016-12-16 9:28 ` Rashi Singhal
2016-12-30 8:25 ` Rashi Singhal
2016-12-30 19:25 ` Eliot Moss
2017-01-03 8:53 Rashi Singhal
2017-01-05 4:04 ` Rashi Singhal
2017-01-05 10:17 ` Mark Geisert
2017-01-06 2:58 ` Rashi Singhal
2017-01-03 11:17 Mark Geisert
[not found] <586F5B5F.1070407@maxrnd.com>
2017-01-06 9:05 ` Mark Geisert
2017-01-06 20:34 ` René Berber
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=2df1b680-a0f4-f7aa-292a-4dbe752e089b@SystematicSw.ab.ca \
--to=brian.inglis@systematicsw.ab.ca \
--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).