xwin segfault on latest cygwin snapshot

Marco Atzeri marco.atzeri@gmail.com
Sun Mar 9 09:47:00 GMT 2014


On 07/03/2014 21:22, Corinna Vinschen wrote:
> On Mar  1 07:45, Marco Atzeri wrote:
>> as it works on 1.7.28 I presume it is a snapshot issue
>>
>> $ uname -srv
>> CYGWIN_NT-6.1-WOW64 1.7.29s(0.271/5/3) 20140228 15:31:43
>
> Was this the first snapshot showing the problem?  If not, which of
> them was the first one?
>
>
> Corinna
>


running starxwin or XWIN

CYGWIN_NT-6.1-WOW64 1.7.29s(0.271/5/3) 20140227 15:33:23
last to work

CYGWIN_NT-6.1-WOW64 1.7.29s(0.271/5/3) 20140228 15:31:43
first to fail

still failing up to
CYGWIN_NT-6.1-WOW64 1.7.29s(0.272/5/3) 20140305 15:33:33



from /var/log/xwin/XWin.0.log

[  4544.589] winInitMultiWindowWM - Calling pthread_mutex_lock ()
[  4544.589] winMultiWindowXMsgProc - Calling pthread_mutex_lock ()
[  4544.605] Fatal signal received in thread 0x80000038
[  4544.605] (EE) Segmentation fault at address 0x0
[  4544.761] (EE) Install xorg-server-debuginfo to get symbol table info 
for backtraces
Attempting backtrace on pid 1208
[  4544.823] (EE)
==================== GDB Backtrace ============


==================== Backtrace ================

==================== Backtrace End ============

[  4544.823] (EE) Fatal server error: (EE) Caught signal 11 
(Segmentation fault). Server aborting
[  4544.823] (EE) Server terminated with error (1). Closing log file.


Regards
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



More information about the Cygwin mailing list