From: "Kunz, Christopher L" <clkunz@sandia.gov>
To: "cygwin@cygwin.com" <cygwin@cygwin.com>
Subject: RE: [EXTERNAL] Re: startxwin - xinit unable to connect to X server
Date: Mon, 18 May 2015 16:43:00 -0000 [thread overview]
Message-ID: <0c4b5ef27b36414bb8e3779e97aabc2e@ES12AMSNLNT.srn.sandia.gov> (raw)
In-Reply-To: <5556348D.7040807@dronecode.org.uk>
Looks like Jon was 100% correct. For me it appears to have been Symantec Endpoint Protection causing the problem. Updated / added exception and the problem has resolved.
Thanks!
-----Original Message-----
From: Jon TURNEY [mailto:jon.turney@dronecode.org.uk]
Sent: Friday, May 15, 2015 11:02
To: Kunz, Christopher L; cygwin@cygwin.com
Subject: Re: [EXTERNAL] Re: startxwin - xinit unable to connect to X server
On 15/05/2015 18:36, Kunz, Christopher L wrote:
> After installing the 64 bit version of Cygwin, I don't experience this problem.
>
> Backtrace output:
>
> gdb: unknown target exception 0x80000001 at 0x5dd96d61
>
> Program received signal ?, Unknown signal.
> [Switching to Thread 8216.0x2374]
> 0x5dd96d61 in sysfer!FirstHookFunc ()
> from /cygdrive/c/Windows/SysWOW64/SYSFER.DLL
> (gdb) bt full
> #0 0x5dd96d61 in sysfer!FirstHookFunc ()
> from /cygdrive/c/Windows/SysWOW64/SYSFER.DLL
> No symbol table info available.
> #1 0x00000000 in ?? ()
> No symbol table info available.
> (gdb)
Thanks.
The injected sysfer.dll belongs to "Symantec Endpoint Protection"
See [1] for a previous incident. As discussed there, I suggest you try updating SEP, or creating an exception for XWin.
[1] https://cygwin.com/ml/cygwin/2015-03/msg00080.html
--
Jon TURNEY
Volunteer Cygwin/X X Server maintainer
prev parent reply other threads:[~2015-05-18 16:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-13 19:06 Kunz, Christopher L
2015-05-14 7:06 ` Bryan Berns
2015-05-15 16:37 ` Jon TURNEY
2015-05-15 18:01 ` [EXTERNAL] " Kunz, Christopher L
2015-05-15 19:08 ` Jon TURNEY
2015-05-18 16:43 ` Kunz, Christopher L [this message]
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=0c4b5ef27b36414bb8e3779e97aabc2e@ES12AMSNLNT.srn.sandia.gov \
--to=clkunz@sandia.gov \
--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).