This is the mail archive of the cygwin-xfree@cygwin.com mailing list for the Cygwin XFree86 project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

RE: [ANNOUNCEMENT] Server Test 71 [DEBUG BUILD]


Of course, pointing to the new debug build would help:

http://www.msu.edu/~huntharo/xwin/shadow/XWin-Test72-DEBUG.exe.bz2

Harold

-----Original Message-----
From: cygwin-xfree-owner@cygwin.com
[mailto:cygwin-xfree-owner@cygwin.com]On Behalf Of Harold L Hunt II
Sent: Friday, January 17, 2003 4:44 PM
To: cygwin-xfree@cygwin.com
Subject: Re: [ANNOUNCEMENT] Server Test 71 [DEBUG BUILD]


I am beginning to think that the

DISPLAY=:0.0

has something to do with these crashes.  If I recall correctly, specifying a
display name such as :0.0 means that you should connect using UNIX domain
sockets, which are emulated in Cygwin using TCP/IP sockets.  We should
change XWin.exe to connect to DISPLAY=127.0.0.1:0.0 and see what happens.

You know... there may be an exit (1) being called in the multi-window
window-manager portions of the code that does not have an error message
being printed out before exit is called.  I will take a peek at the code.  I
suspect that the window manager is unable to connect, so it bails.

Erik --- will you be available to test a DEBUG build in the next few
minutes?

Harold



Erik Frisk wrote:

>On Fri, 17 Jan 2003, Harold L Hunt II wrote:
>
>
>
>>JS,
>>
>>I know what I want you to do:
>>
>>Run XWin.exe without gdb, and send in the last few lines of XWinrl.log.
>>I need to know if the last message in that log is ``calling pthread...''
>>or something else entirely.  By continuing with c in gdb you are kinda
>>throwing us off the trail, because we don't know exactly how far
>>XWin.exe is getting before it runs into problems.
>>
>>
>
>I do not know if I have the same problem as JS, but I experiece the same
>symptom, a crash after a few seconds.
>
>The last lines of XWinrl.log on my machine looks like below.
>I run build: 2003-01-17 - Test72
>
>Regards,
>
>	/Erik
>
>winQueryRGBBitsAndMasks - GetDeviceCaps (BITSPIXEL) returned 24 for the
>screen.
> Using default 24bpp masks.
>winFinishScreenInitFB - Masks: 00ff0000 0000ff00 000000ff
>winInitVisualsShadowGDI - Masks 00ff0000 0000ff00 000000ff BPRGB 8 d 24
>bpp 24
>winCreateDefColormap - Deferring to fbCreateDefColormap ()
>null screen fn ReparentWindow
>null screen fn RestackWindow
>InitQueue - Calling pthread_mutex_init
>InitQueue - pthread_mutex_init returned
>InitQueue - Calling pthread_cond_init
>InitQueue - pthread_cond_init returned
>winScreenInit - returning
>(EE) No primary keyboard configured
>(==) Using compiletime defaults for keyboard
>Rules = "xfree86" Model = "pc101" Layout = "us" Variant = "(null)" Options
>= "(n
>ull)"
>winInitMultiWindowWM - DISPLAY=:0.0
>Could not init font path element /usr/X11R6/lib/X11/fonts/Speedo/,
>removing from
> list!
>Could not init font path element /usr/X11R6/lib/X11/fonts/Type1/, removing
>from
>list!
>Could not init font path element /usr/X11R6/lib/X11/fonts/100dpi/,
>removing from
> list!
>
>
>---------------------------------------------------------------------
>Erik Frisk                            email:         frisk@isy.liu.se
>Dept. of Electrical Engineering         tel:            +46 13 285714
>Linköping University                    fax:            +46 13 282035
>S-581 83 Linköping
>SWEDEN                                       www.fs.isy.liu.se/~frisk
>---------------------------------------------------------------------
>
>
>


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]