From: Ken Brown <kbrown@cornell.edu>
To: Girish Joglekar <girish53@gmail.com>
Cc: cygwin <cygwin@cygwin.com>
Subject: Re: Cygwin 64 problem
Date: Mon, 28 Nov 2016 12:03:00 -0000 [thread overview]
Message-ID: <cf5d53e0-2464-b191-af1b-192cfc0553d9@cornell.edu> (raw)
In-Reply-To: <CAGX=k3HczQGx=51xRwyKrwpKTMqaOVqxj+ud4UH=i1yCPAFGWQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1581 bytes --]
On 11/27/2016 9:03 AM, Girish Joglekar wrote:
> Hi Ken,
> Thank you for your reply on the Cygwin mailing list. I have created a
> slightly smaller test example smaller than what I had created in Feb.
> Attached is a tar file. After make insall if you run TEST.x and click
> the Open button, it gives segmentation fault.
> Hope you will be able to help.
> Thank you.
> Girish
Please keep the discussion on the mailing list so that people who might
be able to help will see it. I personally am not familiar with X11
programming, so I'm not one of those people.
I do have a few comments, however:
1. This may be slightly smaller than your previous program, but it is
still *very* far from a small test case. You really can't expect people
to debug a program of this size for you.
2. I suggest that you build with -Wall (as Marco already suggested in
the earlier discussion) and fix all the compiler warnings. I saw
several that need attention (aside from the many "unused variable"
warnings). It wouldn't hurt to also use -Wextra.
3. I also suggest that you use gdb to find out where the program is
crashing and why. You made a start on that in the discussion last
March, but you didn't follow through. (By the way, I recommend building
without optimization; otherwise you may not be able to get accurate
information about the crash from gdb.)
4. If, after the steps above, you still think the crash is due to a
Cygwin bug rather than a programming error, then try to extract from
your program a test case as small as possible that reproduces the crash.
Ken
[-- Attachment #2: test2.tar --]
[-- Type: application/octet-stream, Size: 686080 bytes --]
[-- Attachment #3: Type: text/plain, Size: 218 bytes --]
--
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 parent reply other threads:[~2016-11-27 16:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAGX=k3HczQGx=51xRwyKrwpKTMqaOVqxj+ud4UH=i1yCPAFGWQ@mail.gmail.com>
2016-11-28 12:03 ` Ken Brown [this message]
2016-11-28 14:34 ` Duncan Roe
2016-11-28 16:19 ` Ken Brown
2016-11-30 3:01 ` Ken Brown
2016-12-04 15:59 ` Ken Brown
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=cf5d53e0-2464-b191-af1b-192cfc0553d9@cornell.edu \
--to=kbrown@cornell.edu \
--cc=cygwin@cygwin.com \
--cc=girish53@gmail.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).