xterm stackdump

Fergus Daly fergusd84@outlook.com
Wed Jul 22 16:04:00 GMT 2020

Lately I have been experiencing an xterm stackdump with varying triggers but all
leading to a forced exit. Here is typical output.

eax=00000092 ebx=80080300 ecx=00000000 edx=00000000 esi=800D4C88 edi=00000000
ebp=00000004 esp=006BC820 program=D:\console32\bin\xterm.exe, pid 1661, thread main
cs=0023 ds=002B es=002B fs=0053 gs=002B ss=002B
Stack trace:
Frame     Function  Args

Identical problem on Windows 10 AND Windows 7. (And that really is unusual. Most
times a problem on W10 is not mimicked on the ultra-robust W7 platform.)
Using cygwin1.dll v.3.1.6 and up-to-datest versions of xinit, xterm, gnuplot, etc.
I can provide output from cygcheck -srv but the file is 1600 lines long and 98K?
Not sure if this is useful / welcome - or how best to transmit it, if it is.

More information about the Cygwin mailing list