[32bit] Xwin 1.17.1.0 broken ?

[32bit] Xwin 1.17.1.0 broken ?

[Marco Atzeri]

last Xwin seems to have broken debug symbols and
it segfaults very early.

64 bit version has debug symbols, and it seems to work fine



$ gdb /usr/bin/XWin.exe
GNU gdb (GDB) 7.8
Copyright (C) 2014 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
<http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "i686-pc-cygwin".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
<http://www.gnu.org/software/gdb/documentation/>.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from /usr/bin/XWin.exe...Reading symbols from 
/usr/lib/debug//usr/bin/XWin.exe.dbg...Can't read data for section 
'.debug_frame' in file '/usr/lib/debug/usr/bin/XWin.exe.dbg'
(gdb) run
Starting program: /usr/bin/XWin.exe
[New Thread 1764.0x1c58]
[New Thread 1764.0x1b3c]
[New Thread 1764.0xba8]
[New Thread 1764.0xe64]
Welcome to the XWin X Server
Vendor: The Cygwin/X Project
Release: 1.17.1.0
OS: CYGWIN_NT-6.1-WOW GE-MATZERI-EU 1.7.35(0.287/5/3) 2015-03-04 12:07 i686
OS: Windows 7 Service Pack 1 [Windows NT 6.1 build 7601] (WoW64)
Package: version 1.17.1-2 built 2015-02-23

winInitializeScreenDefaults - primary monitor w 1600 h 900
winInitializeScreenDefaults - native DPI x 96 y 96
XWin was started with the following command line:

/usr/bin/XWin

(II) xorg.conf is not supported
(II) See http://x.cygwin.com/docs/faq/cygwin-x-faq.html for more information
LoadPreferences: Loading /home/marco/.XWinrc
LoadPreferences: Done parsing the configuration file...
winDetectSupportedEngines - DirectDraw4 installed, allowing ShadowDDNL
winDetectSupportedEngines - Returning, supported engines 00000005
[New Thread 1764.0x638]
gdb: unknown target exception 0x80000001 at 0x73b46661

Program received signal ?, Unknown signal.
[Switching to Thread 1764.0x638]
0x73b46661 in sysfer!FirstHookFunc () from 
/cygdrive/c/Windows/SysWOW64/SYSFER.DLL

--
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

Re: [32bit] Xwin 1.17.1.0 broken ?

[Marco Atzeri]

On 3/5/2015 7:42 PM, Marco Atzeri wrote:
> last Xwin seems to have broken debug symbols and
> it segfaults very early.
>
> 64 bit version has debug symbols, and it seems to work fine
>

As I see no reply, I suspect it is a new performance of my
BLODA Symantec antivirus.

On 32 bit, I am starting to see crazy fault.
And I just noted a curious dll injection.


/usr/local/bin
  $ md5sum.exe pbzip2.exe
dd187b7624975cb104c165e249e092b0 *pbzip2.exe

/usr/local/bin
  $ ldd pbzip2.exe
         ntdll.dll => /cygdrive/c/Windows/SysWOW64/ntdll.dll (0x76fd0000)
         kernel32.dll => /cygdrive/c/Windows/syswow64/kernel32.dll 
(0x76480000)
         KERNELBASE.dll => /cygdrive/c/Windows/syswow64/KERNELBASE.dll 
(0x755e000                        0)
         SYSFER.DLL => /cygdrive/c/Windows/SysWOW64/SYSFER.DLL (0x72af0000)
         UMEngx86.dll => /cygdrive/c/ProgramData/Symantec/Symantec 
Endpoint Prote 
ction/12.1.2015.2015.105/Data/Definitions/BASHDefs/20150224.015/UMEngx86.dll 
(0x                        6cf40000)
         cygbz2-1.dll => /usr/bin/cygbz2-1.dll (0x67680000)
         cygwin1.dll => /usr/bin/cygwin1.dll (0x61000000)
         cyggcc_s-1.dll => /usr/bin/cyggcc_s-1.dll (0x65540000)
         cygstdc++-6.dll => /usr/bin/cygstdc++-6.dll (0x4a600000)

/usr/local/bin
  $ cd /pub/devel/pbzip2/pbzip2-1.1.12-1.i686/build/

/pub/devel/pbzip2/pbzip2-1.1.12-1.i686/build
  $ md5sum.exe pbzip2.exe
dd187b7624975cb104c165e249e092b0 *pbzip2.exe

/pub/devel/pbzip2/pbzip2-1.1.12-1.i686/build
  $ ldd pbzip2.exe
         ntdll.dll => /cygdrive/c/Windows/SysWOW64/ntdll.dll (0x76fd0000)
         kernel32.dll => /cygdrive/c/Windows/syswow64/kernel32.dll 
(0x76480000)
         KERNELBASE.dll => /cygdrive/c/Windows/syswow64/KERNELBASE.dll 
(0x755e0000)
         SYSFER.DLL => /cygdrive/c/Windows/SysWOW64/SYSFER.DLL (0x72af0000)
         cygbz2-1.dll => /usr/bin/cygbz2-1.dll (0x67680000)
         cygwin1.dll => /usr/bin/cygwin1.dll (0x61000000)
         cyggcc_s-1.dll => /usr/bin/cyggcc_s-1.dll (0x65540000)
         cygstdc++-6.dll => /usr/bin/cygstdc++-6.dll (0x4a600000)



--
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

Re: [32bit] Xwin 1.17.1.0 broken ?

[Jon TURNEY]

On 06/03/2015 12:20, Marco Atzeri wrote:
> On 3/5/2015 7:42 PM, Marco Atzeri wrote:
>> last Xwin seems to have broken debug symbols and
>> it segfaults very early.
>>
>> 64 bit version has debug symbols, and it seems to work fine

Sorry, it seems that the debug symbols were broken by compression on 32 bit.

> As I see no reply, I suspect it is a new performance of my
> BLODA Symantec antivirus.
>
> On 32 bit, I am starting to see crazy fault.
> And I just noted a curious dll injection.

This seems likely.  Google suggests injecting sysfer.dll seems to be 
something Synamtic does.

I can't reproduce the segfault.

I hope that there would be other reporters if this wasn't a problem 
local to your machine, but perhaps I am being optimistic.

-- 
Jon TURNEY
Volunteer Cygwin/X X Server maintainer

--
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

Re: [32bit] Xwin 1.17.1.0 broken ?

[Marco Atzeri]

On 3/6/2015 1:39 PM, Jon TURNEY wrote:
> On 06/03/2015 12:20, Marco Atzeri wrote:
>> On 3/5/2015 7:42 PM, Marco Atzeri wrote:
>>> last Xwin seems to have broken debug symbols and
>>> it segfaults very early.
>>>
>>> 64 bit version has debug symbols, and it seems to work fine
>
> Sorry, it seems that the debug symbols were broken by compression on 32
> bit.
>
>> As I see no reply, I suspect it is a new performance of my
>> BLODA Symantec antivirus.
>>
>> On 32 bit, I am starting to see crazy fault.
>> And I just noted a curious dll injection.
>
> This seems likely.  Google suggests injecting sysfer.dll seems to be
> something Synamtic does.
>
> I can't reproduce the segfault.
>
> I hope that there would be other reporters if this wasn't a problem
> local to your machine, but perhaps I am being optimistic.

I just run a Symantec update and the issue seems gone ...

crossing finger.

Marco


--
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

Re: [32bit] Xwin 1.17.1.0 broken ?

[Bill Daily]

The problem is in a Symantec file sysfer.dll.  It seems like it is some type
of Trojan horse that is designed to protect you from other Trojan horses.  I
tried disabling Symantec but am still getting the same error.  After some
more searching on the web I found this page.  


http://www.symantec.com/business/support/index?page=content&id=HOWTO95454

I added XWin.exe to the Application exception list and now it works.





--
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