Re: xterm access violations (again)
On 01/04/2011 17:05, Jim Reisert AD1C wrote: On Sun, Mar 27, 2011 at 1:50 PM, Jim Reisert AD1C wrote: On Sat, Mar 26, 2011 at 12:35 PM, Christopher Faylor wrote: Could someone try this with the latest snapshot? I haven't made any changes but I just want to confirm that it still fails with something close to what will become Cygwin 1.7.9. http://cygwin.com/snapshots/ You just have to replace the DLL. Don't bother with a cygwin-inst* tarball. Yes, still there: How can I/we assist in debugging this problem? First we need to determine where the problem lies, whether it's in Cygwin itself, or xterm. Today it took me 3-4 tries to get an xterm up. As I was running late for work, it was kind of frustrating. I think you could: 1. Obtain the cygwin1.dbg file corresponding to your cygwin1.dll (for snapshots, it is available from the snapshot page, for releases, I believe it is in the corresponding cygwin src package), and place it next to your cygwin1.dll 2. Run xterm under gdb 3. Obtain a backtrace when the segv occurs 4. Diagnose the problem 5. Write and test a patch to fix it You'll probably want to refer to [1] for that last step. :-) [1] http://cygwin.com/contrib.html -- Jon TURNEY Volunteer Cygwin/X X Server maintainer -- 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: xterm access violations (again)
On Mon, Apr 04, 2011 at 02:27:27PM +0100, Jon TURNEY wrote: On 01/04/2011 17:05, Jim Reisert AD1C wrote: On Sun, Mar 27, 2011 at 1:50 PM, Jim Reisert AD1C wrote: On Sat, Mar 26, 2011 at 12:35 PM, Christopher Faylor wrote: Could someone try this with the latest snapshot? I haven't made any changes but I just want to confirm that it still fails with something close to what will become Cygwin 1.7.9. http://cygwin.com/snapshots/ You just have to replace the DLL. Don't bother with a cygwin-inst* tarball. Yes, still there: How can I/we assist in debugging this problem? First we need to determine where the problem lies, whether it's in Cygwin itself, or xterm. Today it took me 3-4 tries to get an xterm up. As I was running late for work, it was kind of frustrating. I think you could: 1. Obtain the cygwin1.dbg file corresponding to your cygwin1.dll (for snapshots, it is available from the snapshot page, for releases, I believe it is in the corresponding cygwin src package), and place it next to your cygwin1.dll 2. Run xterm under gdb 3. Obtain a backtrace when the segv occurs 4. Diagnose the problem 5. Write and test a patch to fix it You'll probably want to refer to [1] for that last step. :-) [1] http://cygwin.com/contrib.html FWIW, I know what is causing the problem but not how to fix it. It's similar to http://cygwin.com/ml/cygwin/2011-04/msg1.html Rebasing should fix that particular problem but it's not a panacea. cgf -- 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: xterm access violations (again)
FWIW, I know what is causing the problem but not how to fix it. It's similar to http://cygwin.com/ml/cygwin/2011-04/msg1.html Rebasing should fix that particular problem but it's not a panacea. The strace output in that other thread shows that GetLastError of 997 formerly caused some pipe handling functions deep in cygwin1.dll to return success and now is converted to an error. 997 is one of the rare non-zero success codes (in some sense). #define ERROR_IO_PENDING 997L Ben Voigt -- 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: xterm access violations (again)
On Sun, Mar 27, 2011 at 1:50 PM, Jim Reisert AD1C jjreis...@alum.mit.edu wrote: On Sat, Mar 26, 2011 at 12:35 PM, Christopher Faylor wrote: Could someone try this with the latest snapshot? I haven't made any changes but I just want to confirm that it still fails with something close to what will become Cygwin 1.7.9. http://cygwin.com/snapshots/ You just have to replace the DLL. Don't bother with a cygwin-inst* tarball. Yes, still there: How can I/we assist in debugging this problem? First we need to determine where the problem lies, whether it's in Cygwin itself, or xterm. Today it took me 3-4 tries to get an xterm up. As I was running late for work, it was kind of frustrating. -- Jim Reisert AD1C, jjreis...@alum.mit.edu, http://www.ad1c.us -- 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: xterm access violations (again)
On Sat, Mar 26, 2011 at 12:35 PM, Christopher Faylor wrote: Could someone try this with the latest snapshot? I haven't made any changes but I just want to confirm that it still fails with something close to what will become Cygwin 1.7.9. http://cygwin.com/snapshots/ You just have to replace the DLL. Don't bother with a cygwin-inst* tarball. Yes, still there: CYGWIN_NT-6.1-WOW64 JJR 1.7.9s(0.236/5/3) 20110327 15:26:47 i686 Cygwin Exception: STATUS_ACCESS_VIOLATION at eip=61020497 eax=00CD00F8 ebx=6124556C ecx=76950D06 edx=00334118 esi= edi=0028F9F4 ebp=61020BE0 esp=0028C7C4 program=D:\cygwin\bin\xterm.exe, pid 7968, thread main cs=0023 ds=002B es=002B fs=0053 gs=002B ss=002B Stack trace: Frame Function Args End of stack trace -- Jim Reisert AD1C, jjreis...@alum.mit.edu, http://www.ad1c.us -- 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: xterm access violations (again)
On Fri, Mar 25, 2011 at 01:22:42AM -0400, Christopher Faylor wrote: On Thu, Mar 24, 2011 at 10:09:38PM -0600, Jim Reisert AD1C wrote: On Thu, Mar 24, 2011 at 5:24 PM, webmaster wrote: http://www.donsbox.com/~dfelicia/xterm-269[redacted] Still dumps, but xterm came up anyway: Exception: STATUS_ACCESS_VIOLATION at eip=61020497 eax=00DD00F8 ebx=61246A44 ecx=75570D06 edx=00334118 esi= edi=0028F9F4 ebp=61020BE0 esp=0028C7C4 program=F:\download\tt\usr\bin\xterm.exe, pid 7796, thread main cs=0023 ds=002B es=002B fs=0053 gs=002B ss=002B Stack trace: Frame Function Args End of stack trace In fact I tried it about 1/2 dozen times. Half the time, no dump, xterm starts. Other half of the time, dump but xterm starts anyway. It's not an xterm problem, AFAICT. It's SEGVing in Cygwin due to a problem with Cygwin's record keeping about loaded DLLs. Possibly rebase will help. I'll investigate more over the weekend. Could someone try this with the latest snapshot? I haven't made any changes but I just want to confirm that it still fails with something close to what will become Cygwin 1.7.9. http://cygwin.com/snapshots/ You just have to replace the DLL. Don't bother with a cygwin-inst* tarball. cgf -- 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: xterm access violations (again)
On Wed, 23 Mar 2011, Yaakov (Cygwin/X) wrote: On Wed, 2011-03-23 at 19:16 -0600, Jim Reisert AD1C wrote: Thomas, that may well be true, but the latest one in the Cygwin repository reports (261). It shows up as 261-1 in setup.exe I just built 269 and will uploaded it with the rest of the X11 updates. thanks -- Thomas E. Dickey http://invisible-island.net ftp://invisible-island.net -- 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: xterm access violations (again)
I just built 269 and will uploaded it with the rest of the X11 updates. Probably in some FAQ and I just can't find it, but where would one get xterm-269.cygport et al. for local building? Some git repository, somewhere? -- 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: xterm access violations (again)
where would one get xterm-269.cygport et al. for local building?Answered my own question: http://cygwin-ports.git.sourceforge.net/git/gitweb.cgi?p=cygwin-ports/xterm;a=summary -- 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: xterm access violations (again)
I just built 269 and will uploaded it with the rest of the X11 updates. It doesn't help. I built using cygport from what you've got in git and I still get: Exception: STATUS_ACCESS_VIOLATION at eip=61020497 eax=00DA80E0 ebx=6124298C ecx=76A10D06 edx=00371D48 esi= edi=0028F9F4 ebp=61020BE0 esp=0028C7C4 program=C:\Cygwin\bin\xterm.exe, pid 672, thread main cs=0023 ds=002B es=002B fs=0053 gs=002B ss=002B Stack trace: Frame Function Args End of stack trace Note that I often (almost always) get this written to xterm.exe.stackdump even when xterm opens successfully. Also note that opening xterms is *much* slower than on XP. -- 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: xterm access violations (again)
On Thu, Mar 24, 2011 at 5:24 PM, webmaster wrote: http://www.donsbox.com/~dfelicia/xterm-269[redacted] Still dumps, but xterm came up anyway: Exception: STATUS_ACCESS_VIOLATION at eip=61020497 eax=00DD00F8 ebx=61246A44 ecx=75570D06 edx=00334118 esi= edi=0028F9F4 ebp=61020BE0 esp=0028C7C4 program=F:\download\tt\usr\bin\xterm.exe, pid 7796, thread main cs=0023 ds=002B es=002B fs=0053 gs=002B ss=002B Stack trace: Frame Function Args End of stack trace In fact I tried it about 1/2 dozen times. Half the time, no dump, xterm starts. Other half of the time, dump but xterm starts anyway. -- Jim Reisert AD1C, jjreis...@alum.mit.edu, http://www.ad1c.us -- 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: xterm access violations (again)
On Thu, Mar 24, 2011 at 10:09:38PM -0600, Jim Reisert AD1C wrote: On Thu, Mar 24, 2011 at 5:24 PM, webmaster wrote: http://www.donsbox.com/~dfelicia/xterm-269[redacted] Still dumps, but xterm came up anyway: Exception: STATUS_ACCESS_VIOLATION at eip=61020497 eax=00DD00F8 ebx=61246A44 ecx=75570D06 edx=00334118 esi= edi=0028F9F4 ebp=61020BE0 esp=0028C7C4 program=F:\download\tt\usr\bin\xterm.exe, pid 7796, thread main cs=0023 ds=002B es=002B fs=0053 gs=002B ss=002B Stack trace: Frame Function Args End of stack trace In fact I tried it about 1/2 dozen times. Half the time, no dump, xterm starts. Other half of the time, dump but xterm starts anyway. It's not an xterm problem, AFAICT. It's SEGVing in Cygwin due to a problem with Cygwin's record keeping about loaded DLLs. Possibly rebase will help. I'll investigate more over the weekend. cgf -- 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: xterm access violations (again)
On Tue, Mar 22, 2011 at 11:28 AM, Jim Reisert AD1C jjreis...@alum.mit.edu wrote: On Tue, Mar 22, 2011 at 11:15 AM, webmaster wrote: After updating to the latest cygwin 1.7.8, today, xterm constantly crashes. cat xterm.exe.stackdump [...] Usually rebaseall fixes this problem, but not this time. I also tried building xterm with cygport, but same result. This is on Windows 7 x64 Professional. On my Win7 system, it crashes about 1/2 the time. If I start it from the system tray icon, and the xterm window doesn't appear in under a second, it has crashed and I try again. This morning it took three tries to get an xterm: Exception: STATUS_ACCESS_VIOLATION at eip=61020497 eax=00B400F8 ebx=612455AC ecx=75570D06 edx=002C4118 esi= edi=0028F9F4 ebp=61020BE0 esp=0028C7C4 program=D:\Cygwin\bin\xterm.exe, pid 8048, thread main cs=0023 ds=002B es=002B fs=0053 gs=002B ss=002B Stack trace: Frame Function Args End of stack trace JJR:~ xterm -v Cygwin 6.8.99.903(261) -- Jim Reisert AD1C, jjreis...@alum.mit.edu, http://www.ad1c.us -- 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: xterm access violations (again)
On Wed, 23 Mar 2011, webmaster wrote: what is xterm -v? $ xterm -v XTerm(261) That's from last June. #263 makes a fix for a problem which might be relevant (and #265 fixes a regression from #263). Note I built myself using cygport so that I could add --disable-narrowproto (See thread with subject Bug: XTerm scrollbar issue last updated 7/13/2010) #269 is current. At the moment, the only fixes I've made against that are minor things (an incomplete change for the fullscreen feature, and an obscure case of a control sequence from #251 changes). -- Thomas E. Dickey http://invisible-island.net ftp://invisible-island.net -- 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: xterm access violations (again)
On Wed, Mar 23, 2011 at 3:17 PM, Thomas Dickey wrote: #269 is current. At the moment, the only fixes I've made against that are minor things (an incomplete change for the fullscreen feature, and an obscure case of a control sequence from #251 changes). Thomas, that may well be true, but the latest one in the Cygwin repository reports (261). It shows up as 261-1 in setup.exe - Jim -- Jim Reisert AD1C, jjreis...@alum.mit.edu, http://www.ad1c.us -- 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: xterm access violations (again)
On Wed, 2011-03-23 at 19:16 -0600, Jim Reisert AD1C wrote: Thomas, that may well be true, but the latest one in the Cygwin repository reports (261). It shows up as 261-1 in setup.exe I just built 269 and will uploaded it with the rest of the X11 updates. Yaakov Cygwin/X -- 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: xterm access violations (again)
On Tue, Mar 22, 2011 at 11:15 AM, webmaster wrote: After updating to the latest cygwin 1.7.8, today, xterm constantly crashes. cat xterm.exe.stackdump [...] Usually rebaseall fixes this problem, but not this time. I also tried building xterm with cygport, but same result. This is on Windows 7 x64 Professional. On my Win7 system, it crashes about 1/2 the time. If I start it from the system tray icon, and the xterm window doesn't appear in under a second, it has crashed and I try again. - Jim -- Jim Reisert AD1C, jjreis...@alum.mit.edu, http://www.ad1c.us -- 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: xterm access violations (again)
On my Win7 system, [xterm] crashes about 1/2 the time. Right. Same, here. It used to crash a lot less frequently. -- 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: xterm access violations (again)
On Tue, 22 Mar 2011, webmaster wrote: On my Win7 system, [xterm] crashes about 1/2 the time. Right. Same, here. It used to crash a lot less frequently. what is xterm -v? (the last crash-related bug I recall was fixed last spring). -- Thomas E. Dickey http://invisible-island.net ftp://invisible-island.net -- 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: xterm access violations (again)
On Tue, Mar 22, 2011 at 11:28 AM, Jim Reisert AD1C jjreis...@alum.mit.edu wrote: On Tue, Mar 22, 2011 at 11:15 AM, webmaster wrote: After updating to the latest cygwin 1.7.8, today, xterm constantly crashes. cat xterm.exe.stackdump [...] Usually rebaseall fixes this problem, but not this time. I also tried building xterm with cygport, but same result. This is on Windows 7 x64 Professional. On my Win7 system, it crashes about 1/2 the time. If I start it from the system tray icon, and the xterm window doesn't appear in under a second, it has crashed and I try again. At work, I'm using the latest version of Cygwin and X server (same versions as at home), but running on a Windows XP system (SP3). I never have any problems. NOTE: the Win7 system at home is 64-bit Pro version. -- Jim Reisert AD1C, jjreis...@alum.mit.edu, http://www.ad1c.us -- 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/
