Mail Archives: cygwin/2015/04/17/04:17:54
--NJSRbAqOy4NeGDns
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
On Apr 16 12:53, Bryan Berns wrote:
> On Thu, Apr 16, 2015 at 10:17 AM, Jim Reisert AD1C
> <jjreisert AT alum DOT mit DOT 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=3D77C50F8A
> > eax=3D00000000 ebx=3D612D67B0 ecx=3D00001000 edx=3D612D2648 esi=3D00000=
000 edi=3D0028C790
> > ebp=3D0028C608 esp=3D0028C604 program=3DC:\Cygwin\bin\XWin.exe, pid 166=
0, thread main
> > cs=3D0023 ds=3D002B es=3D002B fs=3D0053 gs=3D002B ss=3D002B
> > 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 AT alum DOT mit DOT edu>, http://www.ad1c.us
>=20
> 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.
>=20
> 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
--=20
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Maintainer cygwin AT cygwin DOT com
Red Hat
--NJSRbAqOy4NeGDns
Content-Type: application/pgp-signature
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
iQIcBAEBAgAGBQJVMMFiAAoJEPU2Bp2uRE+g2VoQAIO95HdKlbucR7Xy9EB7HPl5
+aPanEyfhGOg0wLk+rXvZkKTwXzD/TYWp0fy6L6L5LBZdmJvbIvoKIIl+2fup8yk
qjrmR73kTXsJ6eD2Qye7q3LMiXlpUw3cGxaviVKm9TY20fnbRbSxX3w8pUVBWimn
97M/EevauTsHkBUTtbZG5e+jpLTxuDv+lYFHfSLvo16hj6qa8AL/BY8YCMKjzfr6
+1yG+K2CsWWuaNfRIabcOkfjupXdLhhDYcFIoLkgkp+MPUcAJsQ550TxtstzjJjU
GMPKkY5pT/VxUoJ7heNpB2pWngNpPB6t1tg6zbYgLQA0PZn2cl9JxLxSPkA7Mc75
uO/7oGIVbT0JUs3Muv5NBGBPvJl65ikNrF0IECRuKgcpHKbQ7e5JC1izNRui4X1p
mBXZeZZjJPUc/Wd3oHsIyqOo1D3WU5be8y22J7ufTAlpqO5PG51LwBqckWp2gxkm
gt+3DsSBMxdoXvMHa96N+pPgcn6T2hTN+7dR89T4PuEE5/DQpBcPxmi4LaceaiF4
KvydhifMrnPN582s1Knt2HSi+z4YB6kIv6In95u+1B6jWW+pr1NXQuqCi8Car6dC
GUozjpitSboVWLzk9JUQrKUAQtDIZigCkdGpj+DYz19I8ADsYmMaCm5+lphGeKq3
/uqyIbUxTkOpe3r8PlA0
=D63K
-----END PGP SIGNATURE-----
--NJSRbAqOy4NeGDns--
- Raw text -