RE: Problem with releases since -37
You did say that and I misread it. I have been looking for a 1.3.23 package and, after checking a half a dozen or so mirrors, have not seen one. Has it been released yet? Is there an ETA? -Andy -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Christopher Faylor Sent: Tuesday, June 03, 2003 10:49 AM To: [EMAIL PROTECTED] Subject: Re: Problem with releases since -37 On Tue, Jun 03, 2003 at 10:38:52AM -0400, Andrew Braverman wrote: I updated the XWin package to -42 and changed nothing else. The new stackdump is attached. Thank you again for all the help. I was talking about the latest CYGWIN DLL, not the latest XWin package. [mailto:[EMAIL PROTECTED] Behalf Of Christopher Faylor Sent: Monday, June 02, 2003 7:44 PM To: [EMAIL PROTECTED] Subject: Re: Problem with releases since -37 On Mon, Jun 02, 2003 at 05:56:19PM -0400, Andrew Braverman wrote: Sorry. Missed that one. It is attached now. Doh. I was hoping that if I saw the cygwin version from the cygcheck output I would be able to figure out the stack dump but I've removed the debugging version of cygwin 1.3.22 that I'd need to do that. If you want to try the latest (i.e., the soon to be uploaded June 2 version) cygwin snapshot DLL and send the stackdump file again, I should be able to say where it is dying from the hex address.
RE: Problem with releases since -37
http://cygwin.com/, in the Contributing section of the left menu, follow the Snapshots link. Igor On Wed, 4 Jun 2003, Andrew Braverman wrote: You did say that and I misread it. I have been looking for a 1.3.23 package and, after checking a half a dozen or so mirrors, have not seen one. Has it been released yet? Is there an ETA? -Andy -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Christopher Faylor Sent: Tuesday, June 03, 2003 10:49 AM To: [EMAIL PROTECTED] Subject: Re: Problem with releases since -37 On Tue, Jun 03, 2003 at 10:38:52AM -0400, Andrew Braverman wrote: I updated the XWin package to -42 and changed nothing else. The new stackdump is attached. Thank you again for all the help. I was talking about the latest CYGWIN DLL, not the latest XWin package. [mailto:[EMAIL PROTECTED] Behalf Of Christopher Faylor Sent: Monday, June 02, 2003 7:44 PM To: [EMAIL PROTECTED] Subject: Re: Problem with releases since -37 On Mon, Jun 02, 2003 at 05:56:19PM -0400, Andrew Braverman wrote: Sorry. Missed that one. It is attached now. Doh. I was hoping that if I saw the cygwin version from the cygcheck output I would be able to figure out the stack dump but I've removed the debugging version of cygwin 1.3.22 that I'd need to do that. If you want to try the latest (i.e., the soon to be uploaded June 2 version) cygwin snapshot DLL and send the stackdump file again, I should be able to say where it is dying from the hex address. -- http://cs.nyu.edu/~pechtcha/ |\ _,,,---,,_[EMAIL PROTECTED] ZZZzz /,`.-'`'-. ;-;;,_[EMAIL PROTECTED] |,4- ) )-,_. ,\ ( `'-' Igor Pechtchanski, Ph.D. '---''(_/--' `-'\_) fL a.k.a JaguaR-R-R-r-r-r-.-.-. Meow! I have since come to realize that being between your mentor and his route to the bathroom is a major career booster. -- Patrick Naughton
RE: Problem with releases since -37
I am usually not this slow. I do know what a snapshot means and that it is not a release and can read when you ask me to change a dll and not the XWin executable. For some reason, I did not process things correctly in the last couple of days. My apologies. I did some more testing based on your suggestions. I first tried the XWin-Test91-DEBUG version of the server with the released version of the dll. That failed as before and gave me a new stackdump. I then put in cygwin1-20030602.dll as /bin/cygwin1.dll. I restarted windows to make sure that the correct dll was used. I ran with the XWin-Test91-DEBUG version of the server again and it gave me Microsoft's do you want to report this box again, but did not produce a stack dump. I tried the 042 version again, and got the same results (do you want to report this and no stackdump). Putting the last working version (037) back in with the new dll works fine. Anyone have any other ideas that I can try? Thanks again for the help so far. - Andy -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Christopher Faylor Sent: Wednesday, June 04, 2003 12:28 PM To: [EMAIL PROTECTED] Subject: Re: Problem with releases since -37 On Wed, Jun 04, 2003 at 09:54:14AM -0400, Andrew Braverman wrote: You did say that and I misread it. I have been looking for a 1.3.23 package and, after checking a half a dozen or so mirrors, have not seen one. Huh? The next version has not been released. Go to the cygwin web site and look for the word Snapshot. A snapshot is not the same as a release. It looks like Harold has done some work with null pointers recently. Maybe that will rectify your problem.
RE: Problem with releases since -37
Howdy Andy.. At 02:37 PM 6/4/2003 -0400, you wrote: I did some more testing based on your suggestions. I first tried the XWin-Test91-DEBUG version of the server with the released version of the dll. That failed as before and gave me a new stackdump. I then put in cygwin1-20030602.dll as /bin/cygwin1.dll. I restarted windows to make sure that the correct dll was used. I ran with the XWin-Test91-DEBUG version of the server again and it gave me Microsoft's do you want to report this box again, but did not produce a stack dump. I tried the 042 version again, and got the same results (do you want to report this and no stackdump). Putting the last working version (037) back in with the new dll works fine. Anyone have any other ideas that I can try? Since nobody seems able to reproduce your failure, you might try debugging it, at least to the point of failure, yourself. You should be able to recompile the XWin.exe in debug mode and start it up in in gdb, and when the crash occurs you should get an annotated function trace with add'l debug info... I think the -DEBUG version is just one with Ralf's new parameter checks, not really a debug version, so you'll really have to recompile with the -g option... -Earle F. Philhower, III [EMAIL PROTECTED] cdrlabel - ZipLabel - FlpLabel http://www.cdrlabel.com
Re: Problem with releases since -37
On Tue, Jun 03, 2003 at 10:38:52AM -0400, Andrew Braverman wrote: I updated the XWin package to -42 and changed nothing else. The new stackdump is attached. Thank you again for all the help. I was talking about the latest CYGWIN DLL, not the latest XWin package. [mailto:[EMAIL PROTECTED] Behalf Of Christopher Faylor Sent: Monday, June 02, 2003 7:44 PM To: [EMAIL PROTECTED] Subject: Re: Problem with releases since -37 On Mon, Jun 02, 2003 at 05:56:19PM -0400, Andrew Braverman wrote: Sorry. Missed that one. It is attached now. Doh. I was hoping that if I saw the cygwin version from the cygcheck output I would be able to figure out the stack dump but I've removed the debugging version of cygwin 1.3.22 that I'd need to do that. If you want to try the latest (i.e., the soon to be uploaded June 2 version) cygwin snapshot DLL and send the stackdump file again, I should be able to say where it is dying from the hex address.
Re: Problem with releases since -37
Andrew, Please do a manual file scan for multiple copies of cygwin1.dll. Don't tell me anything about paths, just do the search and report how many copies you find. For more info specific to this problem, see the following FAQ entry: http://xfree86.cygwin.com/docs/faq/cygwin-xfree-faq.html#q-status-access-violation I wouldn't doubt it if this problem is just exemplified by the new randomness of things that happen in releases after -37. I would actually be surprised if we introduced a bug, since the crash seems to be in cygwin1.dll. Harold Andrew Braverman wrote: I suddenly have a problem running one of the programs that I run all the time. As of release 37, it works fine (I just went back to 37 so that I can run it). The program is ddd (a good graphical debugger, for those who do not know). When running it with versions since 37, it crashes XWin before even displaying the first window. I just tried it with -41 and it still happens. If I debug it, I get the following error: Unhandled exception in XWin.exe (CYGWIN1.DLL): 0xC005: Access Violation. I can get this to happen at will, so if someone wants me to try something, I can do that. I do not, however, currently have source code on my machine. I have the bz2 from setup. Thanks, everyone, for the wonderful product. I appreciate the work you are putting into it. One of these days, I will dig up enough time to get and understand the source code so I can contribute as well. Until then, any help you can give me would be appreciated. Andrew Braverman
Re: Problem with releases since -37
I've just updated to -41 (from -34 or -35, can't remember) and find netscape 4.7 (from a solaris box) frequently crashes Xwin. Other apps like emacs, xterm and xclock (from the same solaris box) seem fine. jeremy PS: Definately only got one cygwin1.dll Andrew Braverman wrote: I suddenly have a problem running one of the programs that I run all the time. As of release 37, it works fine (I just went back to 37 so that I can run it). The program is ddd (a good graphical debugger, for those who do not know). When running it with versions since 37, it crashes XWin before even displaying the first window. I just tried it with -41 and it still happens. If I debug it, I get the following error: Unhandled exception in XWin.exe (CYGWIN1.DLL): 0xC005: Access Violation. I can get this to happen at will, so if someone wants me to try something, I can do that. I do not, however, currently have source code on my machine. I have the bz2 from setup. Thanks, everyone, for the wonderful product. I appreciate the work you are putting into it. One of these days, I will dig up enough time to get and understand the source code so I can contribute as well. Until then, any help you can give me would be appreciated. Andrew Braverman
Re: Problem with releases since -37
Jeremy, Jeremy Wilkins wrote: I've just updated to -41 (from -34 or -35, can't remember) and find netscape 4.7 (from a solaris box) frequently crashes Xwin. Other apps like emacs, xterm and xclock (from the same solaris box) seem fine. Does it just crash XWin.exe, or does it give the STATUS ACCESS VIOLATION dialog box that indicates that the crash occurred in cygwin1.dll? If it is the former, then that is because of a bug in XWin.exe (which I have heard reports of for Netscape before), if it is the later (Andrew's case) then it is probably because of multiple copies of cygwin1.dll on your system. jeremy PS: Definately only got one cygwin1.dll Right, I think you have a different problem. Harold
Re: Problem with releases since -37
Took a little longer to crash this time :) No STATUS ACCESS VIOLATION - just the 'tell microsoft about this crash' box (I'm running XP). I've attached the XWin.log. I'm launching netscape using 'ssh -X [EMAIL PROTECTED] netscape' jeremy Harold L Hunt II wrote: Jeremy, Jeremy Wilkins wrote: I've just updated to -41 (from -34 or -35, can't remember) and find netscape 4.7 (from a solaris box) frequently crashes Xwin. Other apps like emacs, xterm and xclock (from the same solaris box) seem fine. Does it just crash XWin.exe, or does it give the STATUS ACCESS VIOLATION dialog box that indicates that the crash occurred in cygwin1.dll? If it is the former, then that is because of a bug in XWin.exe (which I have heard reports of for Netscape before), if it is the later (Andrew's case) then it is probably because of multiple copies of cygwin1.dll on your system. jeremy PS: Definately only got one cygwin1.dll Right, I think you have a different problem. Harold ddxProcessArgument - Initializing default screens winInitializeDefaultScreens - w 1024 h 768 winInitializeDefaultScreens - Returning OsVendorInit - Creating bogus screen 0 _XSERVTransmkdir: Owner of /tmp/.X11-unix should be set to root (EE) Unable to locate/open config file InitOutput - Error reading config file winDetectSupportedEngines - Windows NT/2000/XP winDetectSupportedEngines - DirectDraw installed winDetectSupportedEngines - Allowing PrimaryDD winDetectSupportedEngines - DirectDraw4 installed winDetectSupportedEngines - Returning, supported engines 001f InitOutput - g_iNumScreens: 1 iMaxConsecutiveScreen: 1 winSetEngine - Multi Window = ShadowGDI winAdjustVideoModeShadowGDI - Using Windows display depth of 32 bits per pixel winCreateBoundingWindowWindowed - User w: 1024 h: 768 winCreateBoundingWindowWindowed - Current w: 1024 h: 768 winAdjustForAutoHide - Original WorkArea: 0 0 739 1024 winAdjustForAutoHide - Adjusted WorkArea: 0 0 739 1024 winCreateBoundingWindowWindowed - WindowClient w 1024 h 739 r 1024 l 0 b 739 t 0 winCreateBoundingWindowWindowed - Returning winAllocateFBShadowGDI - Creating DIB with width: 1024 height: 739 depth: 32 winAllocateFBShadowGDI - Dibsection width: 1024 height: 739 depth: 32 size image: 3026944 winAllocateFBShadowGDI - Created shadow stride: 1024 winFinishScreenInitFB - Masks: 00ff ff00 00ff winInitVisualsShadowGDI - Masks 00ff ff00 00ff BPRGB 8 d 24 bpp 32 winCreateDefColormap - Deferring to fbCreateDefColormap () null screen fn ReparentWindow null screen fn RestackWindow winFinishScreenInitFB - Calling winInitWM. InitQueue - Calling pthread_mutex_init InitQueue - pthread_mutex_init returned InitQueue - Calling pthread_cond_init InitQueue - pthread_cond_init returned winInitWM - Returning. winFinishScreenInitFB - Calling winInitClipboard. winInitMultiWindowWM - Hello winInitClipboard () winFinishScreenInitFB - returning winScreenInit - returning InitOutput - Returning. winInitMultiWindowWM - Calling pthread_mutex_lock () winMultiWindowXMsgProc - Hello winMultiWindowXMsgProc - Calling pthread_mutex_lock () winClipboardProc - Hello winClipboardProc - Calling pthread_mutex_lock () (==) Using preset keyboard for English (United Kingdom) (0809), type 4 (EE) No primary keyboard configured (==) Using compiletime defaults for keyboard Rules = xfree86 Model = pc105 Layout = gb Variant = (null) Options = (null) 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! winPointerWarpCursor - Discarding first warp: 512 369 winBlockHandler - Releasing pmServerStarted winBlockHandler - pthread_mutex_unlock () returned winInitMultiWindowWM - pthread_mutex_lock () returned. DetectUnicodeSupport - Windows NT/2000/XP winInitMultiWindowWM - Calling setlocale () winInitMultiWindowWM - setlocale () returned winInitMultiWindowWM - XInitThreads () returned. winMultiWindowXMsgProc - pthread_mutex_lock () returned. winMultiWindowXMsgProc - XInitThreads () returned. winMultiWindowXMsgProc - pthread_mutex_unlock () returned. winMultiWindowXMsgProc - DISPLAY=127.0.0.1:0.0 winClipboardProc - pthread_mutex_lock () returned. DetectUnicodeSupport - Windows NT/2000/XP winClipboardProc - XInitThreads () returned. winClipboardProc - pthread_mutex_unlock () returned. winClipboardProc - DISPLAY=127.0.0.1:0.0 winInitMultiWindowWM - pthread_mutex_unlock () returned. winInitMultiWindowWM - 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. SelectionNotify - ATOM: PRIMARY winClipboardErrorHandler - ERROR: BadWindow (invalid Window parameter) winClipboardErrorHandler -
RE: Problem with releases since -37
There is only 1 cygwin1.dll anywhere on my system. Just to clarify what happens, I do get the do you want to report this to microsoft box and no specific error message originally. I then choose the debug button, which is when I first see the access violation. Anyone have any other ideas? - Andy -Original Message- From: Harold L Hunt II [mailto:[EMAIL PROTECTED] Sent: Monday, June 02, 2003 10:35 AM To: [EMAIL PROTECTED] Subject: Re: Problem with releases since -37 Andrew, Please do a manual file scan for multiple copies of cygwin1.dll. Don't tell me anything about paths, just do the search and report how many copies you find. For more info specific to this problem, see the following FAQ entry: http://xfree86.cygwin.com/docs/faq/cygwin-xfree-faq.html#q-sta tus-access-violation I wouldn't doubt it if this problem is just exemplified by the new randomness of things that happen in releases after -37. I would actually be surprised if we introduced a bug, since the crash seems to be in cygwin1.dll. Harold Andrew Braverman wrote: I suddenly have a problem running one of the programs that I run all the time. As of release 37, it works fine (I just went back to 37 so that I can run it). The program is ddd (a good graphical debugger, for those who do not know). When running it with versions since 37, it crashes XWin before even displaying the first window. I just tried it with -41 and it still happens. If I debug it, I get the following error: Unhandled exception in XWin.exe (CYGWIN1.DLL): 0xC005: Access Violation. I can get this to happen at will, so if someone wants me to try something, I can do that. I do not, however, currently have source code on my machine. I have the bz2 from setup. Thanks, everyone, for the wonderful product. I appreciate the work you are putting into it. One of these days, I will dig up enough time to get and understand the source code so I can contribute as well. Until then, any help you can give me would be appreciated. Andrew Braverman
Re: Problem with releases since -37
Jeremy, Try running without -clipboard and report your results. Harold Jeremy Wilkins wrote: Took a little longer to crash this time :) No STATUS ACCESS VIOLATION - just the 'tell microsoft about this crash' box (I'm running XP). I've attached the XWin.log. I'm launching netscape using 'ssh -X [EMAIL PROTECTED] netscape' jeremy Harold L Hunt II wrote: Jeremy, Jeremy Wilkins wrote: I've just updated to -41 (from -34 or -35, can't remember) and find netscape 4.7 (from a solaris box) frequently crashes Xwin. Other apps like emacs, xterm and xclock (from the same solaris box) seem fine. Does it just crash XWin.exe, or does it give the STATUS ACCESS VIOLATION dialog box that indicates that the crash occurred in cygwin1.dll? If it is the former, then that is because of a bug in XWin.exe (which I have heard reports of for Netscape before), if it is the later (Andrew's case) then it is probably because of multiple copies of cygwin1.dll on your system. jeremy PS: Definately only got one cygwin1.dll Right, I think you have a different problem. Harold ddxProcessArgument - Initializing default screens winInitializeDefaultScreens - w 1024 h 768 winInitializeDefaultScreens - Returning OsVendorInit - Creating bogus screen 0 _XSERVTransmkdir: Owner of /tmp/.X11-unix should be set to root (EE) Unable to locate/open config file InitOutput - Error reading config file winDetectSupportedEngines - Windows NT/2000/XP winDetectSupportedEngines - DirectDraw installed winDetectSupportedEngines - Allowing PrimaryDD winDetectSupportedEngines - DirectDraw4 installed winDetectSupportedEngines - Returning, supported engines 001f InitOutput - g_iNumScreens: 1 iMaxConsecutiveScreen: 1 winSetEngine - Multi Window = ShadowGDI winAdjustVideoModeShadowGDI - Using Windows display depth of 32 bits per pixel winCreateBoundingWindowWindowed - User w: 1024 h: 768 winCreateBoundingWindowWindowed - Current w: 1024 h: 768 winAdjustForAutoHide - Original WorkArea: 0 0 739 1024 winAdjustForAutoHide - Adjusted WorkArea: 0 0 739 1024 winCreateBoundingWindowWindowed - WindowClient w 1024 h 739 r 1024 l 0 b 739 t 0 winCreateBoundingWindowWindowed - Returning winAllocateFBShadowGDI - Creating DIB with width: 1024 height: 739 depth: 32 winAllocateFBShadowGDI - Dibsection width: 1024 height: 739 depth: 32 size image: 3026944 winAllocateFBShadowGDI - Created shadow stride: 1024 winFinishScreenInitFB - Masks: 00ff ff00 00ff winInitVisualsShadowGDI - Masks 00ff ff00 00ff BPRGB 8 d 24 bpp 32 winCreateDefColormap - Deferring to fbCreateDefColormap () null screen fn ReparentWindow null screen fn RestackWindow winFinishScreenInitFB - Calling winInitWM. InitQueue - Calling pthread_mutex_init InitQueue - pthread_mutex_init returned InitQueue - Calling pthread_cond_init InitQueue - pthread_cond_init returned winInitWM - Returning. winFinishScreenInitFB - Calling winInitClipboard. winInitMultiWindowWM - Hello winInitClipboard () winFinishScreenInitFB - returning winScreenInit - returning InitOutput - Returning. winInitMultiWindowWM - Calling pthread_mutex_lock () winMultiWindowXMsgProc - Hello winMultiWindowXMsgProc - Calling pthread_mutex_lock () winClipboardProc - Hello winClipboardProc - Calling pthread_mutex_lock () (==) Using preset keyboard for English (United Kingdom) (0809), type 4 (EE) No primary keyboard configured (==) Using compiletime defaults for keyboard Rules = xfree86 Model = pc105 Layout = gb Variant = (null) Options = (null) 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! winPointerWarpCursor - Discarding first warp: 512 369 winBlockHandler - Releasing pmServerStarted winBlockHandler - pthread_mutex_unlock () returned winInitMultiWindowWM - pthread_mutex_lock () returned. DetectUnicodeSupport - Windows NT/2000/XP winInitMultiWindowWM - Calling setlocale () winInitMultiWindowWM - setlocale () returned winInitMultiWindowWM - XInitThreads () returned. winMultiWindowXMsgProc - pthread_mutex_lock () returned. winMultiWindowXMsgProc - XInitThreads () returned. winMultiWindowXMsgProc - pthread_mutex_unlock () returned. winMultiWindowXMsgProc - DISPLAY=127.0.0.1:0.0 winClipboardProc - pthread_mutex_lock () returned. DetectUnicodeSupport - Windows NT/2000/XP winClipboardProc - XInitThreads () returned. winClipboardProc - pthread_mutex_unlock () returned. winClipboardProc - DISPLAY=127.0.0.1:0.0 winInitMultiWindowWM - pthread_mutex_unlock () returned. winInitMultiWindowWM - 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
Re: Problem with releases since -37
Are you using -clipboard? Try it without using -clipboard. Harold Andrew Braverman wrote: There is only 1 cygwin1.dll anywhere on my system. Just to clarify what happens, I do get the do you want to report this to microsoft box and no specific error message originally. I then choose the debug button, which is when I first see the access violation. Anyone have any other ideas? - Andy -Original Message- From: Harold L Hunt II [mailto:[EMAIL PROTECTED] Sent: Monday, June 02, 2003 10:35 AM To: [EMAIL PROTECTED] Subject: Re: Problem with releases since -37 Andrew, Please do a manual file scan for multiple copies of cygwin1.dll. Don't tell me anything about paths, just do the search and report how many copies you find. For more info specific to this problem, see the following FAQ entry: http://xfree86.cygwin.com/docs/faq/cygwin-xfree-faq.html#q-sta tus-access-violation I wouldn't doubt it if this problem is just exemplified by the new randomness of things that happen in releases after -37. I would actually be surprised if we introduced a bug, since the crash seems to be in cygwin1.dll. Harold Andrew Braverman wrote: I suddenly have a problem running one of the programs that I run all the time. As of release 37, it works fine (I just went back to 37 so that I can run it). The program is ddd (a good graphical debugger, for those who do not know). When running it with versions since 37, it crashes XWin before even displaying the first window. I just tried it with -41 and it still happens. If I debug it, I get the following error: Unhandled exception in XWin.exe (CYGWIN1.DLL): 0xC005: Access Violation. I can get this to happen at will, so if someone wants me to try something, I can do that. I do not, however, currently have source code on my machine. I have the bz2 from setup. Thanks, everyone, for the wonderful product. I appreciate the work you are putting into it. One of these days, I will dig up enough time to get and understand the source code so I can contribute as well. Until then, any help you can give me would be appreciated. Andrew Braverman
RE: Problem with releases since -37
OK - I tried a few more experiments. I started to experiment outside of my scripts and got down to: XWin -multiwindow I ran an xterm on the Linux host using ssh I ran ddd. Xwin claimed to dump core (though I could not find a core) [1]+ Segmentation fault (core dumped) XWin -multiwindow xterm: fatal IO error 32 (Broken pipe) or KillClient on X server localhost:10.0 There was a stackdump file around that had the following: Exception: STATUS_ACCESS_VIOLATION at eip=61040870 eax= ebx=3030 ecx=10376698 edx= esi=103766A0 edi=103796C8 ebp=0022FB08 esp=0022FAF0 program=C:\cygwinroot\usr\X11R6\bin\XWin.exe cs=001B ds=0023 es=0023 fs=003B gs= ss=0023 Stack trace: Frame Function Args 0022FB08 61040870 (00252D48, 71AB1A51, 00252D48, 00252D48) 0022FB38 610412D6 (103766A0, 0002, 0010, 0022FB58) 0022FB68 6107011B (10376670, 0022FCB0, 002C, 0022FBB4) 0022FB88 6106C5FF (0022FCB0, 0022FBF4, 0022FBD4, 0022FBB4) 0022FD78 6106C094 (00FF, 0075D5F0, 0022FC34, 0022FC14) 0022FE78 00435DBF (102AE960, 0701, FF082020, ) 0022FEA8 00407EDC (0002, , 615F0988, 0001) 0022FEF0 0040179A (0002, 615F0988, 100F0328, 0022FF24) 0022FF40 61007408 (610D1F58, FFFE, 07D0, 610D1E7C) 0022FF90 610076ED (, , 0001, ) 0022FFB0 006FFB82 (00401490, 037F0009, 0022FFF0, 77E814C7) 0022FFC0 0040103C (0022E170, 0001, 7FFDF000, 00450058) 0022FFF0 77E814C7 (00401000, , 78746341, 0020) End of stack trace Though I cannot confirm 100% that ddd did not somehow break the pipe, I can say that it still works on -37. I took a quick look at /tmp/XWin.log and did not find anything that looked like it would be of any help, but I have attached it to this message just in case it is. - Andy -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Harold L Hunt II Sent: Monday, June 02, 2003 2:37 PM To: [EMAIL PROTECTED] Subject: Re: Problem with releases since -37 Are you using -clipboard? Try it without using -clipboard. Harold Andrew Braverman wrote: There is only 1 cygwin1.dll anywhere on my system. Just to clarify what happens, I do get the do you want to report this to microsoft box and no specific error message originally. I then choose the debug button, which is when I first see the access violation. Anyone have any other ideas? - Andy -Original Message- From: Harold L Hunt II [mailto:[EMAIL PROTECTED] Sent: Monday, June 02, 2003 10:35 AM To: [EMAIL PROTECTED] Subject: Re: Problem with releases since -37 Andrew, Please do a manual file scan for multiple copies of cygwin1.dll. Don't tell me anything about paths, just do the search and report how many copies you find. For more info specific to this problem, see the following FAQ entry: http://xfree86.cygwin.com/docs/faq/cygwin-xfree-faq.html#q-sta tus-access-violation I wouldn't doubt it if this problem is just exemplified by the new randomness of things that happen in releases after -37. I would actually be surprised if we introduced a bug, since the crash seems to be in cygwin1.dll. Harold Andrew Braverman wrote: I suddenly have a problem running one of the programs that I run all the time. As of release 37, it works fine (I just went back to 37 so that I can run it). The program is ddd (a good graphical debugger, for those who do not know). When running it with versions since 37, it crashes XWin before even displaying the first window. I just tried it with -41 and it still happens. If I debug it, I get the following error: Unhandled exception in XWin.exe (CYGWIN1.DLL): 0xC005: Access Violation. I can get this to happen at will, so if someone wants me to try something, I can do that. I do not, however, currently have source code on my machine. I have the bz2 from setup. Thanks, everyone, for the wonderful product. I appreciate the work you are putting into it. One of these days, I will dig up enough time to get and understand the source code so I can contribute as well. Until then, any help you can give me would be appreciated. Andrew Braverman XWin.log Description: Binary data
Re: Problem with releases since -37
On Mon, Jun 02, 2003 at 03:16:48PM -0400, Andrew Braverman wrote: OK - I tried a few more experiments. I started to experiment outside of my scripts and got down to: XWin -multiwindow I ran an xterm on the Linux host using ssh I ran ddd. Xwin claimed to dump core (though I could not find a core) [1]+ Segmentation fault (core dumped) XWin -multiwindow xterm: fatal IO error 32 (Broken pipe) or KillClient on X server localhost:10.0 There was a stackdump file around that had the following: Exception: STATUS_ACCESS_VIOLATION at eip=61040870 eax= ebx=3030 ecx=10376698 edx= esi=103766A0 edi=103796C8 ebp=0022FB08 esp=0022FAF0 program=C:\cygwinroot\usr\X11R6\bin\XWin.exe cs=001B ds=0023 es=0023 fs=003B gs= ss=0023 Stack trace: Frame Function Args 0022FB08 61040870 (00252D48, 71AB1A51, 00252D48, 00252D48) 0022FB38 610412D6 (103766A0, 0002, 0010, 0022FB58) 0022FB68 6107011B (10376670, 0022FCB0, 002C, 0022FBB4) 0022FB88 6106C5FF (0022FCB0, 0022FBF4, 0022FBD4, 0022FBB4) 0022FD78 6106C094 (00FF, 0075D5F0, 0022FC34, 0022FC14) 0022FE78 00435DBF (102AE960, 0701, FF082020, ) 0022FEA8 00407EDC (0002, , 615F0988, 0001) 0022FEF0 0040179A (0002, 615F0988, 100F0328, 0022FF24) 0022FF40 61007408 (610D1F58, FFFE, 07D0, 610D1E7C) 0022FF90 610076ED (, , 0001, ) 0022FFB0 006FFB82 (00401490, 037F0009, 0022FFF0, 77E814C7) 0022FFC0 0040103C (0022E170, 0001, 7FFDF000, 00450058) 0022FFF0 77E814C7 (00401000, , 78746341, 0020) End of stack trace Though I cannot confirm 100% that ddd did not somehow break the pipe, I can say that it still works on -37. I took a quick look at /tmp/XWin.log and did not find anything that looked like it would be of any help, but I have attached it to this message just in case it is. How about cygcheck output as per http://cygwin.com/problems.html ? cgf
RE: Problem with releases since -37
Sorry. Missed that one. It is attached now. - Andy -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Christopher Faylor Sent: Monday, June 02, 2003 5:21 PM To: [EMAIL PROTECTED] Subject: Re: Problem with releases since -37 On Mon, Jun 02, 2003 at 03:16:48PM -0400, Andrew Braverman wrote: OK - I tried a few more experiments. I started to experiment outside of my scripts and got down to: XWin -multiwindow I ran an xterm on the Linux host using ssh I ran ddd. Xwin claimed to dump core (though I could not find a core) [1]+ Segmentation fault (core dumped) XWin -multiwindow xterm: fatal IO error 32 (Broken pipe) or KillClient on X server localhost:10.0 There was a stackdump file around that had the following: Exception: STATUS_ACCESS_VIOLATION at eip=61040870 eax= ebx=3030 ecx=10376698 edx= esi=103766A0 edi=103796C8 ebp=0022FB08 esp=0022FAF0 program=C:\cygwinroot\usr\X11R6\bin\XWin.exe cs=001B ds=0023 es=0023 fs=003B gs= ss=0023 Stack trace: Frame Function Args 0022FB08 61040870 (00252D48, 71AB1A51, 00252D48, 00252D48) 0022FB38 610412D6 (103766A0, 0002, 0010, 0022FB58) 0022FB68 6107011B (10376670, 0022FCB0, 002C, 0022FBB4) 0022FB88 6106C5FF (0022FCB0, 0022FBF4, 0022FBD4, 0022FBB4) 0022FD78 6106C094 (00FF, 0075D5F0, 0022FC34, 0022FC14) 0022FE78 00435DBF (102AE960, 0701, FF082020, ) 0022FEA8 00407EDC (0002, , 615F0988, 0001) 0022FEF0 0040179A (0002, 615F0988, 100F0328, 0022FF24) 0022FF40 61007408 (610D1F58, FFFE, 07D0, 610D1E7C) 0022FF90 610076ED (, , 0001, ) 0022FFB0 006FFB82 (00401490, 037F0009, 0022FFF0, 77E814C7) 0022FFC0 0040103C (0022E170, 0001, 7FFDF000, 00450058) 0022FFF0 77E814C7 (00401000, , 78746341, 0020) End of stack trace Though I cannot confirm 100% that ddd did not somehow break the pipe, I can say that it still works on -37. I took a quick look at /tmp/XWin.log and did not find anything that looked like it would be of any help, but I have attached it to this message just in case it is. How about cygcheck output as per http://cygwin.com/problems.html ? cgf cygcheck.out Description: Binary data
Re: Problem with releases since -37
On Mon, Jun 02, 2003 at 05:56:19PM -0400, Andrew Braverman wrote: Sorry. Missed that one. It is attached now. Doh. I was hoping that if I saw the cygwin version from the cygcheck output I would be able to figure out the stack dump but I've removed the debugging version of cygwin 1.3.22 that I'd need to do that. If you want to try the latest (i.e., the soon to be uploaded June 2 version) cygwin snapshot DLL and send the stackdump file again, I should be able to say where it is dying from the hex address. cgf
