From: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
To: cygwin@cygwin.com
Subject: Re: CYGWIN + windos10 + eclipse clp prolog
Date: Wed, 28 Jul 2021 09:26:22 -0600 [thread overview]
Message-ID: <a4559358-8dac-cce0-9112-cdd7b01203a5@SystematicSw.ab.ca> (raw)
In-Reply-To: <VE1PR09MB3551E3FA5D3879C6995607D6B1EA9@VE1PR09MB3551.eurprd09.prod.outlook.com>
On 2021-07-28 02:03, Manu goswami via Cygwin wrote:
> I have previously build eclipse clp prolog several times in CYGWIN
> but suddenly it has started to show ‘SEGMENTATION FAULT’ even after
> fully reinstalling CYGWIN and removing (manually deleting) old
> Cygwin. No error is reported at build time and .exe is successfully
> generated but on execution of .exe file after build shows ‘
> SEGMENTATION FAULT’. Kindly support in resolving most urgently.
Report upstream to wherever you got the sources for whatever "eclipse
clp prolog" is - in whatever language(s) they use - web links to
projects and sources are more informative than garbled buzzwords.
SIGSEGV is a symptom of a programming error - out of bounds access -
caused by following the wrong pointer to an invalid location, using a
NULL pointer, array or buffer index incorrect, use after free, incorrect
object size or indirection, just to suggest some of the most frequent
and common causes.
If you have made your own local and/or recent changes to the sources,
they are invariably the likely cause of the issue, so recheck any recent
local work very carefully.
The Cygwin project provides packages for execution and development but,
as Cygwin is an all volunteer effort, with limited personnel each with
limited time, so all projects built using those packages are the
responsibility of those projects downstream of Cygwin, otherwise we
would not have any time to maintain and expand the packages supported.
--
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada
This email may be disturbing to some readers as it contains
too much technical detail. Reader discretion is advised.
[Data in binary units and prefixes, physical quantities in SI.]
next prev parent reply other threads:[~2021-07-28 15:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-28 8:03 Manu goswami
2021-07-28 15:26 ` Brian Inglis [this message]
2021-07-29 5:26 ` Manu goswami
2021-07-29 7:38 ` Brian Inglis
2021-07-29 11:59 ` Manu goswami
2021-07-29 14:45 ` Brian Inglis
2021-07-31 4:55 ` Manu goswami
2021-07-31 15:56 ` Brian Inglis
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=a4559358-8dac-cce0-9112-cdd7b01203a5@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).