From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: [ANNOUNCEMENT] TEST RELEASE: Cygwin 2.0.0-5
Date: Fri, 17 Apr 2015 08:16:00 -0000 [thread overview]
Message-ID: <20150417081634.GO3657@calimero.vinschen.de> (raw)
In-Reply-To: <CADi7v6JxztfAKqerhSHYhGb22N-OL3Y9nkuvdb_GhsezKTU3zw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2728 bytes --]
On Apr 16 12:53, Bryan Berns wrote:
> On Thu, Apr 16, 2015 at 10:17 AM, Jim Reisert AD1C
> <jjreisert@alum.mit.edu> wrote:
> > I am unable to start Cywin/X X-server 1.17.1 with this version.
> > Previous releases of 2.0.0.x were OK. I had to revert to 1.7.35-1 for
> > the time being.
> >
> > Other than updating to 2.0.0.5, I also installed the April 2015 "Patch
> > Tuesday" updates from Microsoft. I don't know if the two are related.
> > Windows 7 Home Premium, 64-bit
> >
> > Exception: STATUS_ACCESS_VIOLATION at eip=77C50F8A
> > eax=00000000 ebx=612D67B0 ecx=00001000 edx=612D2648 esi=00000000 edi=0028C790
> > ebp=0028C608 esp=0028C604 program=C:\Cygwin\bin\XWin.exe, pid 1660, thread main
> > cs=0023 ds=002B es=002B fs=0053 gs=002B ss=002B
> > Stack trace:
> > Frame Function Args
> > 0028C608 77C50F8A (00000000, 612D2648, 00000000, 612D67B0)
> > 0028C738 610CDA1F (000043FF, 00000000, 00000000, 80012428)
> > 0028C7B8 61047198 (00000000, 72483F24, 75604227, 00000254)
> > 0028C7F8 610F629D (00000001, 00000000, 00000000, 75623912)
> >
> > --
> > Jim Reisert AD1C, <jjreisert@alum.mit.edu>, http://www.ad1c.us
>
> I've actually had problem building Cygwin (1.7.35 or 2.x source) on
> Cygwin 2.x using Windows. The make errors out with a "permissions
> denied" when setting permissions (chmod +x) on config.status in
> <builddir>/etc. I was able to produce it on three different, freshly
> built copies of Windows (no BLODA at all). Only had Cygwin plus the
> build essentials (gcc, ming, xmlto, diffutils, textinfo, cocom)
> installed. Only tried with 32-bit.
>
> The super wacky thing is that if I rearrange the unrelated contents of
> the make file that fuels the whole process, the problem goes away. If
> I "downgrade" the core back to 1.7.35, the problem goes away. It
> almost seems like there might an uninitialized memory issue in the
> code path executed in chmod(). I apologize for the lack of debugging
> on my part, but I just wanted to throw this out there in case a) it
> could be related to this issue or b) anyone else has seen this.
This is more in line with what Ismail reported in
https://cygwin.com/ml/cygwin/2015-04/msg00365.html
And I finally managed to reproduce it. It works on the command line and
only fails during `make' for me. Investigating now...
> That said, I'm making progress in debugging my "Unknown Group" issue
> described in another chain; hope to report out on that this weekend
> when I have a little more time to play.
Cool, thanks.
Corinna
--
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Maintainer cygwin AT cygwin DOT com
Red Hat
[-- Attachment #2: Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2015-04-17 8:16 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-15 16:04 Corinna Vinschen
2015-04-16 14:25 ` Jim Reisert AD1C
2015-04-16 16:21 ` Corinna Vinschen
2015-04-16 16:29 ` Jim Reisert AD1C
2015-04-16 16:38 ` Corinna Vinschen
2015-04-16 21:05 ` Jim Reisert AD1C
2015-04-16 21:17 ` Ian Lambert
2015-04-17 7:38 ` Corinna Vinschen
2015-04-17 13:17 ` Ian Lambert
2015-04-17 16:23 ` Corinna Vinschen
2015-04-16 21:20 ` Jim Reisert AD1C
2015-04-17 7:37 ` Corinna Vinschen
2015-04-16 16:43 ` Corinna Vinschen
2015-04-16 19:49 ` Denis Excoffier
2015-04-17 7:40 ` Corinna Vinschen
2015-04-17 11:29 ` Jon TURNEY
2015-04-17 12:13 ` Corinna Vinschen
2015-04-16 16:53 ` Bryan Berns
2015-04-17 8:16 ` Corinna Vinschen [this message]
2015-04-17 10:07 ` Corinna Vinschen
2015-04-17 10:57 ` Bryan Berns
2015-04-17 11:03 ` Corinna Vinschen
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=20150417081634.GO3657@calimero.vinschen.de \
--to=corinna-cygwin@cygwin.com \
--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).