Danilo,
Thanks for the report. I am working on fixing that problem right now.
Harold
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of Danilo Turina
Sent: Wednesday, January 22, 2003 2:49 AM
To: [EMAIL PROTECTED]
Subject: Re: [ANNOUNCEMENT] Server Test
I tried:
XWin.exe -engine 1
in 24bpp mode crashes
in 32bpp mode works
J S wrote:
Same for me. XWin.exe -engine 1 -rootless crashes.
JS.
> The real problem here may be the way that the GDI DIB engine handles 24
> bpp... not necessarily anything wrong with the MultiWindow mode.
This seems
On Tue, 21 Jan 2003, Harold L Hunt II wrote:
> Erik,
>
> Great! Okay, one last one before I will have to wait until this evening
> to do some debugging of the GDI DIB engine: please run the following and
> report your results:
> XWin.exe -engine 1
crash with the following in XWinrl.log
ddxP
Another crash! Again works OK if I set my display to 16bpp though.
$ ./XWin-Test73-DEBUG.exe -engine 1
Segmentation fault (core dumped)
u752359@A217447D /cygdrive/d/downloads
$ cat /tmp/xwinrl.log
ddxProcessArgument - Initializing default screens
winInitializeDefaultScreens - w 1152 h 864
winInit
JS,
Excellent. Could you please try the following as well:
XWin.exe -engine 1
Thanks so much for testing,
Harold
J S wrote:
And if I change my display to 16 bpp, multiwindow works.
Same for me. XWin.exe -engine 1 -rootless crashes.
JS.
> The real problem here may be the way that
Erik,
Great! Okay, one last one before I will have to wait until this evening
to do some debugging of the GDI DIB engine: please run the following and
report your results:
XWin.exe -engine 1
Thanks so much for testing,
Harold
Erik Frisk wrote:
The real problem here may be the way that the
And if I change my display to 16 bpp, multiwindow works.
Same for me. XWin.exe -engine 1 -rootless crashes.
JS.
> The real problem here may be the way that the GDI DIB engine handles 24
> bpp... not necessarily anything wrong with the MultiWindow mode. This
seems
> quick realistic, sinc
Same for me. XWin.exe -engine 1 -rootless crashes.
JS.
> The real problem here may be the way that the GDI DIB engine handles 24
> bpp... not necessarily anything wrong with the MultiWindow mode. This
seems
> quick realistic, since the GDI DIB engine is not used unless specified
or
> unless
> The real problem here may be the way that the GDI DIB engine handles 24
> bpp... not necessarily anything wrong with the MultiWindow mode. This seems
> quick realistic, since the GDI DIB engine is not used unless specified or
> unless you are using the MultiWindow mode, so a bug in the GDI DIB
ECTED]
Subject: RE: [ANNOUNCEMENT] Server Test 71 [DEBUG BUILD]
Hi Harold, some good news.
I tried it with colordepth 16 and then it worked like a charm. Haven't
tried it more than opening an emacs but that seemed to work just fine.
Do you still want me to try the -clipboard things? (I did n
Hi Harold, some good news.
I tried it with colordepth 16 and then it worked like a charm. Haven't
tried it more than opening an emacs but that seemed to work just fine.
Do you still want me to try the -clipboard things? (I did not use the
-clipboard option in my previous trials, I only started wi
ime that a tiny little bug had something to do with the
color depth.
Thanks so much for testing,
Harold
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of Erik Frisk
Sent: Tuesday, January 21, 2003 4:53 AM
To: [EMAIL PROTECTED]
Subject: RE: [ANNOUNCEMENT] Ser
Hi Harold, here is the latest XWinrl.log for the
XWin-Test73-DEBUG.exe.bz2 binary.
Hope this helps.
Regards,
Erik
winDetectSupportedEngines - DirectDraw4 installed
winDetectSupportedEngines - Returning, supported engines 001f
InitOutput - g_iNumScreens: 1 iMaxConsecutiveScreen: 1
wi
CTED]>
Reply-To: [EMAIL PROTECTED]
To: <[EMAIL PROTECTED]>
Subject: RE: [ANNOUNCEMENT] Server Test 71 [DEBUG BUILD]
Date: Mon, 20 Jan 2003 15:04:35 -0500
MIME-Version: 1.0
Received: from sources.redhat.com ([66.187.233.205]) by
mc3-f14.law16.hotmail.com with Microsoft SMTPSVC(5.0.2195.560
To: [EMAIL PROTECTED]
Subject: RE: [ANNOUNCEMENT] Server Test 71 [DEBUG BUILD]
Thanks for your efforts on this,
> Erik and JS,
>
> Try the new Test73 release (4.2.0-21). The new release has a much more
> robust way of initializing the Multi-Window Window Manager that should
take
&g
Thanks for your efforts on this,
> Erik and JS,
>
> Try the new Test73 release (4.2.0-21). The new release has a much more
> robust way of initializing the Multi-Window Window Manager that should take
> care of your crashes on startup. If not, it should at least allow for
> better reporting o
Erik and JS,
Try the new Test73 release (4.2.0-21). The new release has a much more
robust way of initializing the Multi-Window Window Manager that should take
care of your crashes on startup. If not, it should at least allow for
better reporting of errors.
Do not run Test73 in gdb; that will n
/~huntharo/xwin/shadow/XWin-Test72-DEBUG-2.exe.bz2 (2.8
MiB)
Thanks so much for testing this,
Harold
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of Erik Frisk
Sent: Saturday, January 18, 2003 4:08 PM
To: [EMAIL PROTECTED]
Subject: Re: [ANNOUNCEMENT] Server
Hi Harold,
I tried your DEBUG build just now and unfortunately no change. The end of
XWinrl.log is included at the end of this mail.
I do not know if this is of any help to you experts, but before it crashes
the harddisk becomes very busy for a few seconds and stops when the
XWin-binary core-dum
]
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
4:44 PM
To: [EMAIL PROTECTED]
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
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
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 gd
lf Of Christopher Faylor
Sent: Thursday, January 16, 2003 10:55 AM
To: [EMAIL PROTECTED]
Subject: Re: [ANNOUNCEMENT] Server Test 71 [DEBUG BUILD]
On Thu, Jan 16, 2003 at 08:14:47AM -0500, Harold L Hunt II wrote:
JS,
Looks like we might have a pthreads problem, but I need you to run the
Christopher Faylor wrote:
> It looks like this is dying in a DLL somewhere. 'info dll' should help
> tell what the 0x100f8628 address is related to. However, it would certainly
> help if you built debugging versions of the X DLLs so that symbol info would
> be available. It doesn't seem to be d
libkernel32_a_iname ()
>#13 0x007df252 in cygwin_crt0 ()
>#14 0x0040103c in mainCRTStartup ()
>#15 0x77e992a6 in _libkernel32_a_iname ()
>(gdb) c
>Continuing.
>
>Program exited with code 0305400.
>(gdb) where
>No stack.
>(gdb)
>
>
>>JS,
>>
>>Plea
ng list.
Thanks for testing,
Harold
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of Christopher Faylor
Sent: Thursday, January 16, 2003 10:55 AM
To: [EMAIL PROTECTED]
Subject: Re: [ANNOUNCEMENT] Server Test 71 [DEBUG BUILD]
On Thu, Jan 16, 2003 at 08:14:
AM
To: [EMAIL PROTECTED]
Subject: Re: [ANNOUNCEMENT] Server Test 71 [DEBUG BUILD]
On Thu, Jan 16, 2003 at 08:14:47AM -0500, Harold L Hunt II wrote:
>JS,
>
>Looks like we might have a pthreads problem, but I need you to run the
>new debug build below before I can tell:
There have been s
On Thu, Jan 16, 2003 at 08:14:47AM -0500, Harold L Hunt II wrote:
>JS,
>
>Looks like we might have a pthreads problem, but I need you to run the
>new debug build below before I can tell:
There have been some pthreads fixes in the latest snapshot if anyone
wants to give that a try.
cgf
OK I've done that, and there is DEFINITELY only 1 cygwin1.dll
JS,
Running ``find'' in Cygwin does not search all of your drives, not even all
of your local drives. It only searches within your Cygwin installation
directory.
I want you to go into Windows Explorer, right-click on your C driv
JS,
Running ``find'' in Cygwin does not search all of your drives, not even
all of your local drives. It only searches within your Cygwin
installation directory.
I want you to go into Windows Explorer, right-click on your C drive and
do a search for cygwin1.dll. Then I want you to do it agai
On Thu, 16 Jan 2003, J S wrote:
> Hi Harold,
>
> Is the line below "fbblt.c: No such file or directory" relevant at all?
This means you don't have the sources installed. Or gdb can not find them.
bye
ago
--
[EMAIL PROTECTED]
http://www.gotti.org ICQ: 126018723
Hi Harold,
I'm happy to do the testing, I'm just worried in case we find out it was
something really stupid! Anyway, I'm sure there's only one cygwin1.dll. Is
the line below "fbblt.c: No such file or directory" relevant at all?
$ find / -name cygwin1*
/bin/cygwin1.dll
/usr/bin/cygwin1.dll
$ mo
JS,
Looks like we might have a pthreads problem, but I need you to run the
new debug build below before I can tell:
http://www.msu.edu/~huntharo/xwin/shadow/XWin-Test71-DEBUG-2.exe.bz2
(2.9 MiB)
When you searched your system for multiple copies of cygwin1.dll, you
did search ALL drives (incl
Harold,
Lots of debug info here. I have added more info at the bottom to show what I
get when I run xwin without the -multiwindow flag as well.
$ gdb ./XWin-Test71-DEBUG.exe
GNU gdb 2002-12-19-cvs (cygwin-special)
Copyright 2002 Free Software Foundation, Inc.
GDB is free software, covered by the
Thanks Harold,
I'll have to test it out tomorrow now, as my W2k box is at work.
JS.
Hey, the debug build finished way early.
Try this out:
http://www.msu.edu/~huntharo/xwin/shadow/XWin-Test71-DEBUG.exe.bz2 (2.9
MiB)
Harold
Harold L Hunt II wrote:
I am building a debug version for you.
Colin,
Thanks for the positive report. We are just trying to debug a segfault
on startup problem.
That is indeed how the multi-window mode is supposed to work.
Thanks again,
Harold
Colin Harrison wrote:
All seems OK for me..As a sanity check
I run via startxwin.bat
start XWin :2 -emulate3bu
All seems OK for me..As a sanity check
I run via startxwin.bat
start XWin :2 -emulate3buttons -multiwindow
run xwinclip
run xterm -sl 1000 -sb -leftbar -ms black -fg black -bg white -e /usr/bin/bash
run xsetroot -solid steelblue
and get a minimized 'X Cygwin/XFree86 rl'
with a 'windows framed' '
Hey, the debug build finished way early.
Try this out:
http://www.msu.edu/~huntharo/xwin/shadow/XWin-Test71-DEBUG.exe.bz2 (2.9 MiB)
Harold
Harold L Hunt II wrote:
I am building a debug version for you.
I will post it sometime tonight as an unofficial release (i.e., without
all the formal rel
I am building a debug version for you.
I will post it sometime tonight as an unofficial release (i.e., without
all the formal release announcements, etc.).
Harold
J S wrote:
Yadin,
I tried your suggestion but no success.
JS.
Hi,
This version works great! All the menus are now updated correc
Yadin,
I tried your suggestion but no success.
JS.
Hi,
This version works great! All the menus are now updated correctly (Win XP).
Thanks Kensuke and Harold!
To JS: Are you running any virus protection program? try disabling it.
Yadin.
"Harold L Hunt II" <[EMAIL PROTECTED]> wrote in message
[EM
Hi,
This version works great! All the menus are now updated correctly (Win XP).
Thanks Kensuke and Harold!
To JS: Are you running any virus protection program? try disabling it.
Yadin.
"Harold L Hunt II" <[EMAIL PROTECTED]> wrote in message
[EMAIL PROTECTED]">news:[EMAIL PROTECTED]...
> Links:
>
>
Harold,
My previous patch is for menu problem, not segv.
It sends ConfigureNotify event for clients when window move.
Kensuke Matsuzaki
Links:
I just posted Test 71 to the server development page:
http://xfree86.cygwin.com/devel/shadow/
You can install the Test 71 package via setup.exe by selecting the
'test' package (and be sure to check the 'Bin' box): XFree86-xserv-4.2.0-19
Server Test Series binary and source code releases a
44 matches
Mail list logo
