Yaakov schrieb:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Gerrit P. Haase wrote:
It is uploaded now, could you test, please?
WFM. OT, but does this include the gdk-pixbuf security fix as well?
Yes.
Gerrit
--
=^..^=
On Dec 27 23:15, Gerrit P. Haase wrote:
Yaakov schrieb:
So what we have here looks like something I don't like, which is, that
running gvim requires to run Cygserver because something, gvim itself or
some library, is using SYSV shared memory.
After doing some experimentation, it looks
Yaakov schrieb:
So what we have here looks like something I don't like, which is, that
running gvim requires to run Cygserver because something, gvim itself or
some library, is using SYSV shared memory.
After doing some experimentation, it looks like this isn't a specific
problem with gvim,
Gerrit P. Haase wrote:
Yaakov S (Cygwin Ports) wrote:
After doing some experimentation, it looks like this isn't a specific
problem with gvim, but is common to gtk2 apps, e.g.:
$ CYGWIN= gcolor2
Bad system call
$ gcolor2
[runs]
I don't think that should be necessary, except in very trying
Yaakov S (Cygwin Ports) wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Corinna Vinschen wrote:
The error message you see points to the fact that apparently some part
of gvim or subsequent libraries use SYSV shared memory. The reason you
see this error message and I see a SIGSYS is that
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Corinna Vinschen wrote:
The error message you see points to the fact that apparently some part
of gvim or subsequent libraries use SYSV shared memory. The reason you
see this error message and I see a SIGSYS is that I don't have
CYGWIN=server set
