Re: unixkill crashes under cygwin-1.5.20-1 (and cygwin1dll-20060707)
Corinna Vinschen wrote: On Jul 8 08:32, Lester Ingber wrote: Corinna: I don't understand why I do not have any such crashes under cygwin1dll-1.5.19, but only with cygwin1dll-1.5.20-1 and the latest snapshot cygwin1dll-20060707? May I guess you didn't debug this situation? I did. Trust me. Corinna, was it you that asked about marking the test version of cygwin/x "current"? Now seems like a great time for that. It would probably avoid a zillion identical bug reports to the list. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/
Re: unixkill crashes under cygwin-1.5.20-1 (and cygwin1dll-20060707)
Lester Ingber wrote: Re: 6.8.99.901-1 I understand that, according to the docs, even under Curr, sometimes an experimental version of a package can be seen when toggling. This seems to be case for 6.8.99.901-1 for the xorg-x11 series. However, under Curr, I cannot toggle all of the xorg-x11 packages. Trying to do so keeps switching a few back to 6.8.2.0-4? If I switch to Exp, then all xorg-x11 packages appear as 6.8.99.901-1, while of course pulling in some other Exp versions of other packages. However, the docs are clear that this is not the recommended default, and when starting setup.exe again, the Curr default will overwrite such packages if they were selected. So, what exactly is recommended? If the crash on exit is a problem for you, install the experimental version and see how it works for you. If you do so, you will need to remember to toggle the experimental packages you updated to "Keep" on all subsequent invocations of setup.exe until these packages, or later ones containing the same fix, get promoted to current. If the crash isn't a problem for you, just stick with the current version until a new version become current. -- Larry Hall http://www.rfk.com RFK Partners, Inc. (508) 893-9779 - RFK Office 216 Dalton Rd. (508) 893-9889 - FAX Holliston, MA 01746 -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/
Re: unixkill crashes under cygwin-1.5.20-1 (and cygwin1dll-20060707)
Re: 6.8.99.901-1
I understand that, according to the docs, even under Curr, sometimes an
experimental version of a package can be seen when toggling. This seems
to be case for 6.8.99.901-1 for the xorg-x11 series.
However, under Curr, I cannot toggle all of the xorg-x11 packages.
Trying to do so keeps switching a few back to 6.8.2.0-4?
If I switch to Exp, then all xorg-x11 packages appear as 6.8.99.901-1,
while of course pulling in some other Exp versions of other packages.
However, the docs are clear that this is not the recommended default,
and when starting setup.exe again, the Curr default will overwrite such
packages if they were selected.
So, what exactly is recommended?
Thanks.
Lester
+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=
Just how can I can out of x-windoes without a crash dump? If I right
click on the X icon and Exit, I get the same beahvior as if I use
unixkill?
Or, is this bug (that I have only since in cygwin1.dll-1.5.20-1 and
cygwin1.dll-20060707) such that this occurs no matter how one exits.
The statement below says this is fixed in 6.8.99.901.
Also, under setup.exe, under Curr, my default for the latest X server
is 6.8.2.0-4. If I toggle New, one of the options is 6.8.99.901-1?
The statement below implies that this is the more recent version?
Thanks.
Lester
+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=
On Jul 8 08:32, Lester Ingber wrote:
> Corinna:
>
> I don't understand why I do not have any such crashes under
> cygwin1dll-1.5.19, but only with cygwin1dll-1.5.20-1 and the latest
> snapshot cygwin1dll-20060707?
May I guess you didn't debug this situation? I did. Trust me.
Corinna
+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=
Corinna:
I don't understand why I do not have any such crashes under
cygwin1dll-1.5.19, but only with cygwin1dll-1.5.20-1 and the latest
snapshot cygwin1dll-20060707?
I attach the output of cygcheck -s -v -r > cygcheck.out
which I took with cygwin1dll-1.5.19.
Thanks.
Lester
+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=
Date: Tue, 4 Jul 2006 22:36:30 +0200
On Jul 4 13:21, Lester Ingber wrote:
> Has anyone else noticed that unixkill crashes under cygwin-1.5.20-1?
> When I press CNTL-ALT-BKSP, I do not get a confirmation prompt, my
> X windows do close, but I get an XWin.exe.stackdump -file and after
> getting out of Cygwin CNTL-ALT-DEL shows som hanging tcsh processes
> (my primary shell).
This is a bug in the confirmation dialog routine in the 6.8.2.0
X server. That's fixed in 6.8.99.901.
Corinna
+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=
* From: Corinna Vinschen
* To: cygwin-xfree at cygwin dot com
* Date: Sat, 8 Jul 2006 18:08:36 +0200
* Subject: Re: unixkill crashes under cygwin-1.5.20-1 (and
cygwin1dll-20060707)
* References: <[EMAIL PROTECTED]>
* Reply-to: cygwin-xfree at cygwin dot com
* Reply-to: cygwin-xfree at cygwin dot com
On Jul 8 08:32, Lester Ingber wrote:
> Corinna:
>
> I don't understand why I do not have any such crashes under
> cygwin1dll-1.5.19, but only with cygwin1dll-1.5.20-1 and the latest
> snapshot cygwin1dll-20060707?
May I guess you didn't debug this situation? I did. Trust me.
Corinna
--
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Project Co-Leader cygwin AT cygwin DOT com
Red Hat
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://x.cygwin.com/docs/
FAQ: http://x.cygwin.com/docs/faq/
Re: unixkill crashes under cygwin-1.5.20-1 (and cygwin1dll-20060707)
Just how can I can out of x-windoes without a crash dump? If I right
click on the X icon and Exit, I get the same beahvior as if I use
unixkill?
Or, is this bug (that I have only since in cygwin1.dll-1.5.20-1 and
cygwin1.dll-20060707) such that this occurs no matter how one exits.
The statement below says this is fixed in 6.8.99.901.
Under setup.exe, under Curr, my default for the latest X server
is 6.8.2.0-4. If I toggle New, one of the options is 6.8.99.901-1?
The statement below implies that this is the more recent version?
Thanks.
Lester
+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=
On Jul 8 08:32, Lester Ingber wrote:
> Corinna:
>
> I don't understand why I do not have any such crashes under
> cygwin1dll-1.5.19, but only with cygwin1dll-1.5.20-1 and the latest
> snapshot cygwin1dll-20060707?
May I guess you didn't debug this situation? I did. Trust me.
Corinna
+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=
Corinna:
I don't understand why I do not have any such crashes under
cygwin1dll-1.5.19, but only with cygwin1dll-1.5.20-1 and the latest
snapshot cygwin1dll-20060707?
I attach the output of cygcheck -s -v -r > cygcheck.out
which I took with cygwin1dll-1.5.19.
Thanks.
Lester
+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=
Date: Tue, 4 Jul 2006 22:36:30 +0200
On Jul 4 13:21, Lester Ingber wrote:
> Has anyone else noticed that unixkill crashes under cygwin-1.5.20-1?
> When I press CNTL-ALT-BKSP, I do not get a confirmation prompt, my
> X windows do close, but I get an XWin.exe.stackdump -file and after
> getting out of Cygwin CNTL-ALT-DEL shows som hanging tcsh processes
> (my primary shell).
This is a bug in the confirmation dialog routine in the 6.8.2.0
X server. That's fixed in 6.8.99.901.
Corinna
+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=
* From: Corinna Vinschen
* To: cygwin-xfree at cygwin dot com
* Date: Sat, 8 Jul 2006 18:08:36 +0200
* Subject: Re: unixkill crashes under cygwin-1.5.20-1 (and
cygwin1dll-20060707)
* References: <[EMAIL PROTECTED]>
* Reply-to: cygwin-xfree at cygwin dot com
* Reply-to: cygwin-xfree at cygwin dot com
On Jul 8 08:32, Lester Ingber wrote:
> Corinna:
>
> I don't understand why I do not have any such crashes under
> cygwin1dll-1.5.19, but only with cygwin1dll-1.5.20-1 and the latest
> snapshot cygwin1dll-20060707?
May I guess you didn't debug this situation? I did. Trust me.
Corinna
--
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Project Co-Leader cygwin AT cygwin DOT com
Red Hat
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://x.cygwin.com/docs/
FAQ: http://x.cygwin.com/docs/faq/
Re: unixkill crashes under cygwin-1.5.20-1 (and cygwin1dll-20060707)
On Jul 8 08:32, Lester Ingber wrote: > Corinna: > > I don't understand why I do not have any such crashes under > cygwin1dll-1.5.19, but only with cygwin1dll-1.5.20-1 and the latest > snapshot cygwin1dll-20060707? May I guess you didn't debug this situation? I did. Trust me. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/
Re: unixkill crashes under cygwin-1.5.20-1
On Jul 4 13:21, Lester Ingber wrote: > Has anyone else noticed that unixkill crashes under cygwin-1.5.20-1? > When I press CNTL-ALT-BKSP, I do not get a confirmation prompt, my > X windows do close, but I get an XWin.exe.stackdump -file and after > getting out of Cygwin CNTL-ALT-DEL shows som hanging tcsh processes > (my primary shell). This is a bug in the confirmation dialog routine in the 6.8.2.0 X server. That's fixed in 6.8.99.901. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/
unixkill crashes under cygwin-1.5.20-1
Has anyone else noticed that unixkill crashes under cygwin-1.5.20-1? When I press CNTL-ALT-BKSP, I do not get a confirmation prompt, my X windows do close, but I get an XWin.exe.stackdump -file and after getting out of Cygwin CNTL-ALT-DEL shows som hanging tcsh processes (my primary shell). I start wy windows from a Cygwin window with XWin -notrayicon -unixkill -clipboard -multiwindow & in my modified /usr/local/bin/startxwin.sh file, also attached. I attach the log of the failed session and the crash file. Thanks. Lester -- Prof. Lester Ingber [EMAIL PROTECTED] [EMAIL PROTECTED] www.ingber.comalumnus.caltech.edu/~ingber Exception: STATUS_ACCESS_VIOLATION at eip=610DBE48 eax= ebx=0014 ecx=0005 edx= esi=0075CB7C edi= ebp=0022A680 esp=0022A674 program=C:\cygwin\usr\X11R6\bin\XWin.exe, pid 4108, thread main cs=001B ds=0023 es=0023 fs=003B gs= ss=0023 Stack trace: Frame Function Args 0022A680 610DBE48 (, 0075CB7C, 0014, 0022A718) 0022A6C0 610F412C (0022D008, 0022C318, 0022C038, 0001) 0022A6E0 610DF590 (0022C038, 0022AC86, 0075CB90, 0001) 0022C300 610E0FAE (0022D008, 0022C318, 0075CB7C, 0022C3A4) 0022C390 610E34EF (, 0075CB7C, 0003, 000F042B) 0022C3C0 610916B8 (00250652, 0110, 002A0686, 00A2B330) 0022C3EC 77D48734 (0044FB40, 00250652, 0110, 002A0686) 0022C458 77D545E4 (, 0044FB40, 00250652, 0110) 0022C4A0 77D53FD9 (, 0110, 002A0686, 00A2B330) 0022C4BC 77D6E571 (00250652, 0110, 002A0686, 00A2B330) 0022C4E8 77D48734 (77D6E54F, 00250652, 0110, 002A0686) 0022C550 77D48816 (, 77D6E54F, 00250652, 0110) 0022C58C 77D4B89B (00C9E830, 40C92088, 002A0686, 00A2B330) 0022C644 77D54E28 (, 40C9E830, 021C, 00250652) 0022C668 77D5514C (0040, 007C8DDC, 0011067A, 0044FB40) 0022C694 77D6C7FD (0040, 0075CB70, 0011067A, 0044FB40) End of stack trace (more stack frames may be present) [1] 2136 Welcome to the XWin X Server Vendor: The Cygwin/X Project Release: 6.8.2.0-4 Contact: cygwin-xfree@cygwin.com XWin was started with the following command line: XWin -notrayicon -unixkill -clipboard -multiwindow _XSERVTransmkdir: Cannot create /tmp/.X11-unix with root ownership winValidateArgs - g_iNumScreens: 1 iMaxConsecutiveScreen: 1 (II) XF86Config is not supported (II) See http://x.cygwin.com/docs/faq/cygwin-x-faq.html for more information (==) FontPath set to "/usr/X11R6/lib/X11/fonts/misc/,/usr/X11R6/lib/X11/fonts/TTF/,/usr/X11R6/lib/X11/fonts/Type1/,/usr/X11R6/lib/X11/fonts/CID/,/usr/X11R6/lib/X11/fonts/75dpi/,/usr/X11R6/lib/X11/fonts/100dpi/" winPrefsLoadPreferences: /home/ingber/.XWinrc winDetectSupportedEngines - Windows NT/2000/XP winDetectSupportedEngines - DirectDraw installed winDetectSupportedEngines - DirectDraw4 installed winDetectSupportedEngines - Returning, supported engines 0007 winSetEngine - Multi Window or Rootless => ShadowGDI winAdjustVideoModeShadowGDI - Using Windows display depth of 32 bits per pixel winAllocateFBShadowGDI - Creating DIB with width: 1600 height: 1200 depth: 32 winFinishScreenInitFB - Masks: 00ff ff00 00ff winInitVisualsShadowGDI - Masks 00ff ff00 00ff BPRGB 8 d 24 bpp 32 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 winInitMultiWindowWM - Hello winInitMultiWindowWM - Calling pthread_mutex_lock () winMultiWindowXMsgProc - Hello winMultiWindowXMsgProc - Calling pthread_mutex_lock () MIT-SHM extension disabled due to lack of kernel support XFree86-Bigfont extension local-client optimization disabled due to lack of shared memory support in the kernel (--) Setting autorepeat to delay=500, rate=31 (--) winConfigKeyboard - Layout: "0409" (0409) (--) Using preset keyboard for "English (USA)" (409), type "4" Rules = "xorg" Model = "pc105" Layout = "us" Variant = "(null)" Options = "(null)" (--) 3 mouse buttons found Could not init font path element /usr/X11R6/lib/X11/fonts/CID/, removing from list! winPointerWarpCursor - Discarding first warp: 800 600 winInitMultiWindowWM - pthread_mutex_lock () returned. winProcEstablishConnection - Hello winInitClipboard () winClipboardProc - Hello winProcEstablishConnection - winInitClipboard returned. DetectUnicodeSupport - Windows NT/2000/XP winMultiWindowXMsgProc - pthread_mutex_lock () returned. winInitMultiWindowWM - pthread_mutex_unlock () returned. winInitMultiWindowWM - DISPLAY=127.0.0.1:0.0 winMultiWindowXMsgProc - pthread_mutex_unlock () returned. winClipboardProc - DISPLAY=127.0.0.1:0.0 winMultiWindowXMsgProc - DISPLAY=127.0.0.1:0.0 winInitMultiWindowWM - XOpenDisplay () returned and successfully opened the display. winClipboardProc - XO
