From: Ken Brown <kbrown@cornell.edu>
To: "cygwin@cygwin.com" <cygwin@cygwin.com>
Subject: Re: setup-x86.exe v2.893 has stopped working
Date: Tue, 02 Oct 2018 19:36:00 -0000 [thread overview]
Message-ID: <d33edbea-d849-bda7-5ea6-b9aeda12be5c@cornell.edu> (raw)
In-Reply-To: <CAFWoy7HURnK9vX35V2PEL5jG3JKSMv+UpgOpKXnGcteEGPPbUA@mail.gmail.com>
On 10/2/2018 2:47 PM, Keith Christian wrote:
> 32 bit has been working on this 64 bit machine for the last several
> years. This is the setup program, why is it suddenly having problems?
There may be a bug in the program that happened to be triggered by what you were
doing.
> Didn't see anything out of the ordinary in setup.log, setup.log.full,
> or in the "cygcheck -s -r -v" output. What debugging info is
> available for the setup program itself beyond setup.log* ?
Do you know how to use gdb? If so, I could make a debugging version of setup
available to you (or maybe you could build it yourself?).
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:[~2018-10-02 19:36 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-02 16:12 Keith Christian
2018-10-02 17:32 ` Marco Atzeri
2018-10-02 18:48 ` Keith Christian
2018-10-02 19:24 ` cyg Simple
2018-10-03 13:49 ` Keith Christian
2018-10-02 19:36 ` Ken Brown [this message]
2018-10-02 20:30 ` Jon Turney
2018-10-03 13:55 ` Keith Christian
2018-10-03 14:03 ` Marco Atzeri
2018-10-03 15:40 ` Keith Christian
2018-10-03 16:53 ` Jon Turney
2018-10-03 16:54 ` Jon Turney
2018-10-03 22:32 ` Keith Christian
2018-10-04 18:43 ` Jon Turney
2018-10-05 3:07 ` Keith Christian
2018-10-13 18:19 ` Jon Turney
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=d33edbea-d849-bda7-5ea6-b9aeda12be5c@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).