From: Ken Brown <kbrown@cornell.edu>
To: cygwin@cygwin.com
Subject: Re: Application not working in 64-bit cygwin cygwin/X
Date: Mon, 28 Nov 2016 07:07:00 -0000 [thread overview]
Message-ID: <39a3c4f5-7d98-f24a-a21b-1cbe4ce1ec8f@cornell.edu> (raw)
In-Reply-To: <CAGX=k3FawzaCnzgUORdKdNb+DXoJdvLN6JwUno5Gnnj414aR-Q@mail.gmail.com>
On 11/26/2016 6:51 PM, Girish Joglekar wrote:
> I had submitted a possible bug report in March 2016 and a link to tar
> file with source code. David Stacey had reproduced my problem. I
> downloaded the latest version of cygwin two days ago. The problem
> still persists. Can some one advise me whether I should expect some
> help from the cygwin experts. I can submit the source code again if
> necessary.
If you think your crash is due to a Cygwin bug, then you need to try to
write a small test case that exhibits the problem. Marco told you that
last February, and this was your reply
(https://cygwin.com/ml/cygwin/2016-02/msg00368.html):
> The code is so interlinked that it would have taken me
> a lot longer to separate out only the relevant code.
You have to show some willingness to spend time on this problem yourself
if you hope to get help from the Cygwin experts.
Ken
--
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-11-27 3:04 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-27 22:30 Girish Joglekar
2016-11-28 7:07 ` Ken Brown [this message]
-- strict thread matches above, loose matches on Subject: below --
2016-03-16 21:38 Girish Joglekar
2016-03-11 14:23 Girish Joglekar
2016-03-11 23:10 ` David Stacey
2016-03-12 6:28 ` Marco Atzeri
2016-03-12 17:39 ` Kaz Kylheku
2016-03-12 18:50 ` Corinna Vinschen
2016-03-15 13:14 ` cyg Simple
2016-03-10 15:58 Girish Joglekar
2016-03-10 16:06 ` Marco Atzeri
2016-03-10 17:05 ` Jon Turney
2016-02-23 16:35 Girish Joglekar
2016-02-23 15:12 Girish Joglekar
2016-02-23 15:51 ` Marco Atzeri
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=39a3c4f5-7d98-f24a-a21b-1cbe4ce1ec8f@cornell.edu \
--to=kbrown@cornell.edu \
--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).