Re: Emacs problem with Cygwin 1.5.17-1 (rebasing)
I want to complete the story which has some point of interest. Obviously, you are not obliged to replay, not to take care of problems. As you can see from this mailing list, after installing the cygwin package 1.5.17-1 (26-27 May) I had a problem with Emacs: it took all CPU (100%) and its window did not appear, but downgrading to 1.5.16-1 Emacs worked fine. After many attemps to solve the problem I decided to reinstall ALL Cygwin from scratch (i.e. deleting C:\cygwin, key registry etc.) I had almost all packages installed (only gcc-test-suite, ghostscript native, regex and xwinclip was not installed). After this reinstall (good news) EMACS WORKED FINE with Cygwin 1.5.17-1!!! (Also Emacs 21.3.50-2-test worked!) Now the bad news. Seeing these good things, I decided to reinstall others X-applications. In particular I reinstalled ROOT which is a CERN applications. Normally I rebuild and install it. This application has some tests that I run after every rebuild. Between these tests, there is a program (stress.exe) that, with some Cygwin version (not always), has a core dump: unable to remap... and the problem is caused by some DLL. (in this case: *** unable to remap C:\cygwin\usr\X11R6\bin\cygXpm-4.dll to same address as parent(0x2B7) != 0x2B8 173 [main] stress 1084 fork_parent: child 1184 died waiting for dll loading and Aborted (core dumped) ) It is more than an year that I have discovered the cure to this: run the command rebaseall -v from a std bash shell (as suggested me someone from the mailing list). === So even this time I have rebased and the test work, but...Emacs DOES NOT!!! i.e. after rebasing Emacs has the some problems described above. === With the versions of Cygwin, previous to 1.5.17-1, there were not problems in rebasing. Best regards angelo.
Re: Emacs problem with Cygwin 1.5.17-1 (rebasing)
I want to complete the story which has some point of interest. Obviously, you are not obliged to replay, not to take care of problems. As you can see from this mailing list, after installing the cygwin package 1.5.17-1 (26-27 May) I had a problem with Emacs: it took all CPU (100%) and its window did not appear, but downgrading to 1.5.16-1 Emacs worked fine. After many attemps to solve the problem I decided to reinstall ALL Cygwin from scratch (i.e. deleting C:\cygwin, key registry etc.) I had almost all packages installed (only gcc-test-suite, ghostscript native, regex and xwinclip was not installed). After this reinstall (good news) EMACS WORKED FINE with Cygwin 1.5.17-1!!! (Also Emacs 21.3.50-2-test worked!) Now the bad news. Seeing these good things, I decided to reinstall others X-applications. In particular I reinstalled ROOT which is a CERN applications. Normally I rebuild and install it. This application has some tests that I run after every rebuild. Between these tests, there is a program (stress.exe) that, with some Cygwin version (not always), has a core dump: unable to remap... and the problem is caused by some DLL. (in this case: *** unable to remap C:\cygwin\usr\X11R6\bin\cygXpm-4.dll to same address as parent(0x2B7) != 0x2B8 173 [main] stress 1084 fork_parent: child 1184 died waiting for dll loading and Aborted (core dumped) ) It is more than an year that I have discovered the cure to this: run the command rebaseall -v from a std bash shell (as suggested me someone from the mailing list). === So even this time I have rebased and the test work, but...Emacs DOES NOT!!! i.e. after rebasing Emacs has the some problems described above. === With the versions of Cygwin, previous to 1.5.17-1, there were not problems in rebasing. Best regards angelo. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: Emacs problem with Cygwin 1.5.17-1
No one is obligated but when one one is asked for something: http://cygwin.com/ml/cygwin-xfree/2005-05/msg00270.html and one answers http://cygwin.com/ml/cygwin-xfree/2005-05/msg00274.html it is natural to wait for a response, a simple response as Ok received! or sometghing else only to close the cycle. Best regards, Angelo Graziosi On Thu, 2 Jun 2005, Larry Hall wrote: At 01:37 PM 6/2/2005, you wrote: On Wed, 1 Jun 2005 19:09:35 -0400 , Christopher Faylor wrote: Please stop doing this. I do read email. I will read your email when I have time. Pinging me is not going to help. You should at least answer OK. the problem is under investigation or something else. This isn't a customer support line. It's volunteer. While most postings to this list receive some sort of response at some time, no one is obligated to respond to any posts. If this policy proves to be a problem for you, you, of course, aren't obligated to post on this list. Also, paid Cygwin support contracts are available through Red Hat at least. You may want to consider that option if you want quick and consistent response times. -- Larry Hall http://www.rfk.com RFK Partners, Inc. (508) 893-9779 - RFK Office 838 Washington Street (508) 893-9889 - FAX Holliston, MA 01746 -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: Emacs problem with Cygwin 1.5.17-1
On Fri, Jun 03, 2005 at 10:02:09PM +0200, Angelo Graziosi wrote: No one is obligated but when one one is asked for something: http://cygwin.com/ml/cygwin-xfree/2005-05/msg00270.html and one answers http://cygwin.com/ml/cygwin-xfree/2005-05/msg00274.html it is natural to wait for a response, a simple response as Ok received! or sometghing else only to close the cycle. The nature of mailing lists are such that you can pretty much assume that, if you send it to a mailing list, it has been received. However, if you are going to argue about the way I've chosen to help, I think I'll just say nevermind, then. Perhaps some other, more responsive individual would like to take over. cgf -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: Emacs problem with Cygwin 1.5.17-1
Thanks for the rapid communications I have resolve downgrading to 1.5.16-1. angelo. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: Emacs problem with Cygwin 1.5.17-1
On Wed, 1 Jun 2005 19:09:35 -0400 , Christopher Faylor wrote: Please stop doing this. I do read email. I will read your email when I have time. Pinging me is not going to help. You should at least answer OK. the problem is under investigation or something else. angelo. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: Emacs problem with Cygwin 1.5.17-1
At 01:37 PM 6/2/2005, you wrote: On Wed, 1 Jun 2005 19:09:35 -0400 , Christopher Faylor wrote: Please stop doing this. I do read email. I will read your email when I have time. Pinging me is not going to help. You should at least answer OK. the problem is under investigation or something else. This isn't a customer support line. It's volunteer. While most postings to this list receive some sort of response at some time, no one is obligated to respond to any posts. If this policy proves to be a problem for you, you, of course, aren't obligated to post on this list. Also, paid Cygwin support contracts are available through Red Hat at least. You may want to consider that option if you want quick and consistent response times. -- Larry Hall http://www.rfk.com RFK Partners, Inc. (508) 893-9779 - RFK Office 838 Washington Street (508) 893-9889 - FAX Holliston, MA 01746 -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: Emacs problem with Cygwin 1.5.17-1 (CGF, a little comment)
http://cygwin.com/ml/cygwin-xfree/2005-05/msg00274.html best regards angelo.
Re: Emacs problem with Cygwin 1.5.17-1 (CGF, a little comment)
http://cygwin.com/ml/cygwin-xfree/2005-05/msg00274.html best regards angelo. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: Emacs problem with Cygwin 1.5.17-1 (CGF, a little comment)
On Wed, Jun 01, 2005 at 11:51:34PM +0200, Angelo Graziosi wrote: http://cygwin.com/ml/cygwin-xfree/2005-05/msg00274.html Please stop doing this. I do read email. I will read your email when I have time. Pinging me is not going to help. cgf -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: Emacs problem with Cygwin 1.5.17-1
On Sun, May 29, 2005 at 02:49:31PM +0200, Angelo Graziosi wrote: --- Here is some answer to --- --- http://cygwin.com/ml/cygwin-xfree/2005-05/msg00261.html --- --- --- With TASKMANAGER Emacs takes from 97% to 99% of CPU. --- --- Using your hints I have noted that if I do not start Emacs --- the command --- ---procps auwx --- --- prints the data an returns to prompt. --- --- If I start Emacs the result is: --- --- [EMAIL PROTECTED] ~ $ emacs [1] 1492 [EMAIL PROTECTED] ~ $ ps PIDPPIDPGID WINPID TTY UIDSTIME COMMAND 1448 11448 1448 con 500 13:05:15 /usr/X11R6/bin/XWin 1364 11364 1364 con 500 13:05:19 /usr/bin/xterm 138413641384 14360 500 13:05:22 /usr/bin/bash 149213841492 14160 500 13:06:27 /usr/bin/emacs 158013841580 15720 500 13:06:30 /usr/bin/ps [EMAIL PROTECTED] ~ $ procps auwx USER PID %CPU %MEMVSZ RSS TTY STAT START TIME COMMAND 500 1448 1.4 4.2 6812 11068 tty0 Ss 13:05 0:01 /usr/X11R6/bin/XWin -multiwindow -clipboard -silent-dup-error +bs 500 1364 0.6 2.8 4296 7376 tty0 Rs 13:05 0:00 /usr/bin/xterm -e /usr/bin/bash -l -ms red -fg lightgray -bg black 500 1384 0.2 1.5 1620 4016 tty0 Ss 13:05 0:00 /usr/bin/bash -l --- --- ... and after many minutes (i.e. after I lunched!): --- 500 1492 107 2.9 7320 7752 tty0 R13:06 0:10 defunct 500 1564 1.0 1.4 2260 3676 tty0 R13:06 0:00 procps This shows that emacs wasn't spinning although it was using some CPU. Other than that, there is nothing here which helps figure out why you are having problems. Is there anything in the X log file? --- What does WJFFM mean? http://cygwin.com/acronyms/#WJFFM cgf
Re: Emacs problem with Cygwin 1.5.17-1
I remember you, that reinstalling Cygwin 1.5-16-1 (and keeping coreutils 5.3.0-6) Emacs works fine. I would keep 1.5.17-1 because it allow me to build CERNLIB-2005 with a limited number of patches (with 1.5.16-1 there is something more to patch) I have also tried XEmacs 21.4.17-1. It starts and the window shows itself, apparently without problems. Now XWin.log Thanks angelo. Welcome to the XWin X Server Vendor: The Cygwin/X Project Release: 6.8.2.0-2 Contact: cygwin-xfree@cygwin.com XWin was started with the following command line: /usr/X11R6/bin/XWin -multiwindow -clipboard -silent-dup-error +bs ddxProcessArgument - Initializing default screens winInitializeDefaultScreens - w 800 h 600 winInitializeDefaultScreens - Returning _XSERVTransmkdir: Cannot create /tmp/.X11-unix with root ownership (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/ winAdjustVideoModeShadowGDI - Using Windows display depth of 32 bits per pixel winAllocateFBShadowGDI - Creating DIB with width: 800 height: 600 depth: 32 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 winMultiWindowXMsgProc - Hello winInitMultiWindowWM - Calling pthread_mutex_lock () 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=250, rate=31 (--) winConfigKeyboard - Layout: 0410 (0410) (--) Using preset keyboard for Italian (410), type 4 (--) 3 mouse buttons found Could not init font path element /usr/X11R6/lib/X11/fonts/CID/, removing from list! winInitMultiWindowWM - pthread_mutex_lock () returned. winProcEstablishConnection - Hello winMultiWindowXMsgProc - pthread_mutex_lock () returned. winInitMultiWindowWM - pthread_mutex_unlock () returned. winMultiWindowXMsgProc - pthread_mutex_unlock () returned. winInitMultiWindowWM - DISPLAY=127.0.0.1:0.0 winMultiWindowXMsgProc - DISPLAY=127.0.0.1:0.0 winInitClipboard () winProcEstablishConnection - winInitClipboard returned. winClipboardProc - Hello DetectUnicodeSupport - Windows NT/2000/XP winClipboardProc - DISPLAY=127.0.0.1:0.0 winInitMultiWindowWM - XOpenDisplay () returned and successfully opened the display. winClipboardProc - XOpenDisplay () returned and successfully opened the display. winMultiWindowXMsgProc - XOpenDisplay () returned and successfully opened the display.
Re: Emacs problem with Cygwin 1.5.17-1
I remember you, that reinstalling Cygwin 1.5-16-1 (and keeping coreutils 5.3.0-6) Emacs works fine. I would keep 1.5.17-1 because it allow me to build CERNLIB-2005 with a limited number of patches (with 1.5.16-1 there is something more to patch) I have also tried XEmacs 21.4.17-1. It starts and the window shows itself, apparently without problems. Now XWin.log Thanks angelo. Welcome to the XWin X Server Vendor: The Cygwin/X Project Release: 6.8.2.0-2 Contact: cygwin-xfree@cygwin.com XWin was started with the following command line: /usr/X11R6/bin/XWin -multiwindow -clipboard -silent-dup-error +bs ddxProcessArgument - Initializing default screens winInitializeDefaultScreens - w 800 h 600 winInitializeDefaultScreens - Returning _XSERVTransmkdir: Cannot create /tmp/.X11-unix with root ownership (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/ winAdjustVideoModeShadowGDI - Using Windows display depth of 32 bits per pixel winAllocateFBShadowGDI - Creating DIB with width: 800 height: 600 depth: 32 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 winMultiWindowXMsgProc - Hello winInitMultiWindowWM - Calling pthread_mutex_lock () 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=250, rate=31 (--) winConfigKeyboard - Layout: 0410 (0410) (--) Using preset keyboard for Italian (410), type 4 (--) 3 mouse buttons found Could not init font path element /usr/X11R6/lib/X11/fonts/CID/, removing from list! winInitMultiWindowWM - pthread_mutex_lock () returned. winProcEstablishConnection - Hello winMultiWindowXMsgProc - pthread_mutex_lock () returned. winInitMultiWindowWM - pthread_mutex_unlock () returned. winMultiWindowXMsgProc - pthread_mutex_unlock () returned. winInitMultiWindowWM - DISPLAY=127.0.0.1:0.0 winMultiWindowXMsgProc - DISPLAY=127.0.0.1:0.0 winInitClipboard () winProcEstablishConnection - winInitClipboard returned. winClipboardProc - Hello DetectUnicodeSupport - Windows NT/2000/XP winClipboardProc - DISPLAY=127.0.0.1:0.0 winInitMultiWindowWM - XOpenDisplay () returned and successfully opened the display. winClipboardProc - XOpenDisplay () returned and successfully opened the display. winMultiWindowXMsgProc - XOpenDisplay () returned and successfully opened the display. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: Emacs problem with Cygwin 1.5.17-1 (CGF please comment)
I pointed out a problem between Emacs (21.2-13, i.e. curr.) and Cygwin 1.5.17-1. You asked me others informations at which I replied: http://cygwin.com/ml/cygwin-xfree/2005-05/msg00264.html What are your comments? Thanks angelo.
Re: Emacs problem with Cygwin 1.5.17-1 (CGF please comment) (fwd)
-- Forwarded message -- Date: Mon, 30 May 2005 19:07:56 +0200 (MET DST) From: Angelo Graziosi [EMAIL PROTECTED] To: cygwin-xfree@cygwin.com Subject: Re: Emacs problem with Cygwin 1.5.17-1 (CGF please comment) I pointed out a problem between Emacs (21.2-13, i.e. curr.) and Cygwin 1.5.17-1. You asked me others informations at which I replied: http://cygwin.com/ml/cygwin-xfree/2005-05/msg00264.html What are your comments? Thanks angelo. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: Emacs problem with Cygwin 1.5.17-1
On Sat, May 28, 2005 at 09:14:24PM +0200, Angelo Graziosi wrote: With Cygwin 1.5.17-1, after starting XWin (startxwin.bat) and Emacs, the Emacs window does not show itself, i.e. $ emacs [1] 1776 but the emacs window does not appear! The ps command shows: $ ps PIDPPIDPGID WINPID TTY UIDSTIME COMMAND 1380 11380 1380 con 500 20:45:19 /usr/X11R6/bin/XWin 1436 11436 1436 con 500 20:45:23 /usr/bin/xterm 142414361424 15160 500 20:45:26 /usr/bin/bash 8241424 824 14520 500 20:52:15 /usr/bin/ssh 1228 11228 1228 con 500 21:01:17 /usr/bin/xterm 129212281292 17041 500 21:01:17 /usr/bin/bash 177612921776 16881 500 21:01:28 /usr/bin/emacs 162412921624 16761 500 21:03:07 /usr/bin/ps i.e. emacs seems to be loaded. These things happen as Administrator and NOT-Administrator user. WJFFM. Does procps auwx show if the emacs is consuming CPU? If you do a strace -ppidofemacs does anything interesting show up? Also please provide cygcheck output, as an attachment. cgf
