Re: xterm access violations (again)

[Christopher Faylor <cgf-use-the-mailinglist-please at cygwin dot com>]

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=00000000 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/