Re: graph (plotutils) seg-faulting
On Wed, 22 Jul 2020 20:10:44 +0200 Marco Atzeri via Cygwin wrote: > If it is NOT a Bloda than may be it is Windows itself. Well I know that my work computer is running a lot of crap to "protect" me. I tried to go through and start disabling it today, and as you might guess I can't. I have since upgraded win10 and i'm still seeing the same problem. And probably important to mention that my home win 10 box has no problems. Certainly on my work laptop it's probably a case of BLODA. BTW, i had a broken latex install that i couldn't figure out so i re-installed cygwin again, and that fixed my latex problem but graph was still broken. -- Brian -- Problem reports: https://cygwin.com/problems.html FAQ: https://cygwin.com/faq/ Documentation:https://cygwin.com/docs.html Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple
Re: graph (plotutils) seg-faulting
On 23.07.2020 00:12, Ken Brown via Cygwin wrote: On 7/22/2020 6:07 PM, Tony Richardson via Cygwin wrote: On Wed, Jul 22, 2020 at 3:48 PM Marco Atzeri via Cygwin wrote: On 22.07.2020 14:06, Ken Brown via Cygwin wrote: On 7/22/2020 1:36 AM, Marco Atzeri via Cygwin wrote: On 22.07.2020 02:10, Tony Richardson via Cygwin wrote: I have attached both the cygcheck and strace output. Tony Richardson something is clearly interfering with your Cygwin installation --- Process 11136 loaded C:\Applications\cygwin64\bin\cygwin1.dll at 00c8 --- Process 11136 unloaded DLL at 00c8 I can reproduce the problem on my system: $ strace graph ... Segmentation fault I thought that simply rebuilding plotutils might fix the problem, but there were a lot of compilation warnings, and the build failed. Some of the warnings look serious to me, but I have no idea if they could cause Windows to try to load DLLs at strange addresses. Ken -- Hi Ken, I rebuilt and uploaded a test version 2.6-6 only for 64bit try to see if something change Regards Marco I tried the test version, unfortunately it still segfaults for me. no surprise. It was unlikely to work Same for me. I'm also getting strange output from ldd, but maybe that's just another manifestation of the same problem: $ ldd /usr/bin/graph ntdll.dll => /c/WINDOWS/SYSTEM32/ntdll.dll (0x7ff82a4c) KERNEL32.DLL => /c/WINDOWS/System32/KERNEL32.DLL (0x7ff8289c) KERNELBASE.dll => /c/WINDOWS/System32/KERNELBASE.dll (0x7ff8280c) cygplot-2.dll => /usr/bin/cygplot-2.dll (0x9f) cygplot-2.dll => /usr/bin/cygplot-2.dll (0xbf) cygplot-2.dll => /usr/bin/cygplot-2.dll (0xbf) cygwin1.dll => /usr/bin/cygwin1.dll (0xd2) [...] cygintl-8.dll => /usr/bin/cygintl-8.dll (0x176) cygintl-8.dll => /usr/bin/cygintl-8.dll (0x176) cygiconv-2.dll => /usr/bin/cygiconv-2.dll (0x178) cygiconv-2.dll => /usr/bin/cygiconv-2.dll (0x178) Ken -- can you check with cat /proc/self/maps Usually I see locale.nls loaded verylow 0001-0002 rw-s : 0 [win heap 1 default shared] 0003-0004D000 r--s : 0 0005-00054000 r--s : 0 0006-00061000 r--s : 0 0007-00072000 rw-p : 0 0008-00149000 r--s 98EE:C713 281474977436242 /cygdrive/c/Windows/System32/locale.nls 0015-00152000 rw-p : 0 [win heap 0 default grow] 00152000-00182000 ===p 2000 : 0 [win heap 0 default grow] the program itself 10040-100401000 r--p D603:FB6E 281474976713960 /usr/bin/cat.exe 100401000-100406000 r-xp 1000 D603:FB6E 281474976713960 /usr/bin/cat.exe 100406000-100407000 rw-p 6000 D603:FB6E 281474976713960 /usr/bin/cat.exe 100407000-10040C000 r--p 7000 D603:FB6E 281474976713960 /usr/bin/cat.exe 10040C000-10040F000 rw-p C000 D603:FB6E 281474976713960 /usr/bin/cat.exe 10040F000-10041 r--p F000 D603:FB6E 281474976713960 /usr/bin/cat.exe 18001-18002 rw-s : 0 [procinfo] 18002-180029000 rw-s : 0 [cygwin-user-shared] 18003-18003C000 rw-s : 0 [cygwin-shared] loading area for cygwin DLLs 18004-180041000 r--p D603:FB6E 1688849860266440 /usr/bin/cygwin1.dll 180041000-180229000 r-xp 1000 D603:FB6E 1688849860266440 /usr/bin/cygwin1.dll 180229000-18022D000 rwxp 001E9000 D603:FB6E 1688849860266440 /usr/bin/cygwin1.dll 18022D000-180266000 rw-p 001ED000 D603:FB6E 1688849860266440 /usr/bin/cygwin1.dll 180266000-1802EA000 r--p 00226000 D603:FB6E 1688849860266440 /usr/bin/cygwin1.dll 1802EA000-180322000 rw-p 002AA000 D603:FB6E 1688849860266440 /usr/bin/cygwin1.dll 180322000-180331000 r--p 002E2000 D603:FB6E 1688849860266440 /usr/bin/cygwin1.dll 180331000-180342000 rw-p 002F1000 D603:FB6E 1688849860266440 /usr/bin/cygwin1.dll 180342000-180343000 r--p 00302000 D603:FB6E 1688849860266440 /usr/bin/cygwin1.dll 180343000-18065 rw-p 00303000 D603:FB6E 1688849860266440 /usr/bin/cygwin1.dll 3CC3A-3CC3A1000 r--p D603:FB6E 281474976713233 /usr/bin/cygintl-8.dll 3CC3A1000-3CC3A8000 r-xp 1000 D603:FB6E 281474976713233 /usr/bin/cygintl-8.dll 3CC3A8000-3CC3A9000 rw-p 8000 D603:FB6E 281474976713233 /usr/bin/cygintl-8.dll 3CC3A9000-3CC3AE000 r--p 9000 D603:FB6E 281474976713233 /usr/bin/cygintl-8.dll 3CC3AE000-3CC3AF000 rw-p E000 D603:FB6E 281474976713233 /usr/bin/cygintl-8.dll 3CC3AF000-3CC3B r--p F000 D603:FB6E 281474976713233 /usr/bin/cygintl-8.dll 3CC3B-3CC3B2000 rw-p 0001 D603:FB6E 281474976713233 /usr/bin/cygintl-8.dll 3CC3B2000-3CC3B4000 r--p 00012000 D603:FB6E 281474976713233 /usr/bin/cygintl-8.dll 3D969-3D9691000 r--p D603:FB6E 281474976713163 /usr/bin/c
Re: graph (plotutils) seg-faulting
On 7/22/2020 6:07 PM, Tony Richardson via Cygwin wrote: On Wed, Jul 22, 2020 at 3:48 PM Marco Atzeri via Cygwin wrote: On 22.07.2020 14:06, Ken Brown via Cygwin wrote: On 7/22/2020 1:36 AM, Marco Atzeri via Cygwin wrote: On 22.07.2020 02:10, Tony Richardson via Cygwin wrote: I have attached both the cygcheck and strace output. Tony Richardson something is clearly interfering with your Cygwin installation --- Process 11136 loaded C:\Applications\cygwin64\bin\cygwin1.dll at 00c8 --- Process 11136 unloaded DLL at 00c8 I can reproduce the problem on my system: $ strace graph ... Segmentation fault I thought that simply rebuilding plotutils might fix the problem, but there were a lot of compilation warnings, and the build failed. Some of the warnings look serious to me, but I have no idea if they could cause Windows to try to load DLLs at strange addresses. Ken -- Hi Ken, I rebuilt and uploaded a test version 2.6-6 only for 64bit try to see if something change Regards Marco I tried the test version, unfortunately it still segfaults for me. Same for me. I'm also getting strange output from ldd, but maybe that's just another manifestation of the same problem: $ ldd /usr/bin/graph ntdll.dll => /c/WINDOWS/SYSTEM32/ntdll.dll (0x7ff82a4c) KERNEL32.DLL => /c/WINDOWS/System32/KERNEL32.DLL (0x7ff8289c) KERNELBASE.dll => /c/WINDOWS/System32/KERNELBASE.dll (0x7ff8280c) cygplot-2.dll => /usr/bin/cygplot-2.dll (0x9f) cygplot-2.dll => /usr/bin/cygplot-2.dll (0xbf) cygplot-2.dll => /usr/bin/cygplot-2.dll (0xbf) cygwin1.dll => /usr/bin/cygwin1.dll (0xd2) [...] cygintl-8.dll => /usr/bin/cygintl-8.dll (0x176) cygintl-8.dll => /usr/bin/cygintl-8.dll (0x176) cygiconv-2.dll => /usr/bin/cygiconv-2.dll (0x178) cygiconv-2.dll => /usr/bin/cygiconv-2.dll (0x178) Ken -- Problem reports: https://cygwin.com/problems.html FAQ: https://cygwin.com/faq/ Documentation:https://cygwin.com/docs.html Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple
Re: graph (plotutils) seg-faulting
On Wed, Jul 22, 2020 at 3:48 PM Marco Atzeri via Cygwin wrote: > On 22.07.2020 14:06, Ken Brown via Cygwin wrote: > > On 7/22/2020 1:36 AM, Marco Atzeri via Cygwin wrote: > >> On 22.07.2020 02:10, Tony Richardson via Cygwin wrote: > >>> I have attached both the cygcheck and strace output. > >>> > >>> Tony Richardson > >>> > >> > >> something is clearly interfering with your Cygwin installation > >> > >> --- Process 11136 loaded C:\Applications\cygwin64\bin\cygwin1.dll at > >> 00c8 > >> --- Process 11136 unloaded DLL at 00c8 > > > > I can reproduce the problem on my system: > > > > $ strace graph > ... > > > Segmentation fault > > > > > > I thought that simply rebuilding plotutils might fix the problem, but > > there were a lot of compilation warnings, and the build failed. Some of > > the warnings look serious to me, but I have no idea if they could cause > > Windows to try to load DLLs at strange addresses. > > > > Ken > > -- > > Hi Ken, > I rebuilt and uploaded a test version 2.6-6 only for 64bit > try to see if something change > > Regards > Marco > I tried the test version, unfortunately it still segfaults for me. Tony -- Problem reports: https://cygwin.com/problems.html FAQ: https://cygwin.com/faq/ Documentation:https://cygwin.com/docs.html Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple
Re: graph (plotutils) seg-faulting
On 22.07.2020 14:06, Ken Brown via Cygwin wrote: On 7/22/2020 1:36 AM, Marco Atzeri via Cygwin wrote: On 22.07.2020 02:10, Tony Richardson via Cygwin wrote: I have attached both the cygcheck and strace output. Tony Richardson something is clearly interfering with your Cygwin installation --- Process 11136 loaded C:\Applications\cygwin64\bin\cygwin1.dll at 00c8 --- Process 11136 unloaded DLL at 00c8 I can reproduce the problem on my system: $ strace graph ... Segmentation fault I thought that simply rebuilding plotutils might fix the problem, but there were a lot of compilation warnings, and the build failed. Some of the warnings look serious to me, but I have no idea if they could cause Windows to try to load DLLs at strange addresses. Ken -- Hi Ken, I rebuilt and uploaded a test version 2.6-6 only for 64bit try to see if something change Regards Marco -- Problem reports: https://cygwin.com/problems.html FAQ: https://cygwin.com/faq/ Documentation:https://cygwin.com/docs.html Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple
Re: graph (plotutils) seg-faulting
On 22.07.2020 18:30, Tony Richardson wrote: On Wed, Jul 22, 2020 at 12:36 AM Marco Atzeri via Cygwin mailto:cygwin@cygwin.com>> wrote: On 22.07.2020 02:10, Tony Richardson via Cygwin wrote: > I have attached both the cygcheck and strace output. > > Tony Richardson > something is clearly interfering with your Cygwin installation --- Process 11136 loaded C:\Applications\cygwin64\bin\cygwin1.dll at 00c8 --- Process 11136 unloaded DLL at 00c8 I only appear to have problems with graph. Everything else seems to work fine. Tony Hi Tony very strange. I have not touched graph by ages https://sourceware.org/pipermail/cygwin-announce/2016-April/006984.html and of all the libraries used by it nothing was recently updated. $ cygcheck /usr/bin/graph.exe D:\cygwin64\bin\graph.exe D:\cygwin64\bin\cygplot-2.dll D:\cygwin64\bin\cygwin1.dll C:\WINDOWS\system32\KERNEL32.dll C:\WINDOWS\system32\ntdll.dll C:\WINDOWS\system32\KERNELBASE.dll D:\cygwin64\bin\cygpng16-16.dll D:\cygwin64\bin\cygz.dll D:\cygwin64\bin\cygX11-6.dll D:\cygwin64\bin\cygxcb-1.dll D:\cygwin64\bin\cygXau-6.dll D:\cygwin64\bin\cygXdmcp-6.dll D:\cygwin64\bin\cygXaw-7.dll D:\cygwin64\bin\cygXext-6.dll D:\cygwin64\bin\cyggcc_s-seh-1.dll D:\cygwin64\bin\cygXmu-6.dll D:\cygwin64\bin\cygXt-6.dll D:\cygwin64\bin\cygICE-6.dll D:\cygwin64\bin\cygSM-6.dll D:\cygwin64\bin\cyguuid-1.dll D:\cygwin64\bin\cygintl-8.dll D:\cygwin64\bin\cygiconv-2.dll D:\cygwin64\bin\cygXpm-4.dll If it is NOT a Bloda than may be it is Windows itself. Marco -- Problem reports: https://cygwin.com/problems.html FAQ: https://cygwin.com/faq/ Documentation:https://cygwin.com/docs.html Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple
Re: xterm stackdump
On 22.07.2020 18:04, Fergus Daly via Cygwin wrote: Lately I have been experiencing an xterm stackdump with varying triggers but all leading to a forced exit. Here is typical output. Exception: STATUS_INTEGER_DIVIDE_BY_ZERO at eip=0045D5EF eax=0092 ebx=80080300 ecx= edx= esi=800D4C88 edi= ebp=0004 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. -- just add the cygcheck.out as attachment. is segfaulting every time or just some time ? Can you run it under strace ? DISPLAY=":0.0" strace -o xterm.strace /usr/bin/xterm.exe Regards Marco -- Problem reports: https://cygwin.com/problems.html FAQ: https://cygwin.com/faq/ Documentation:https://cygwin.com/docs.html Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple
Re: graph (plotutils) seg-faulting
On Wed, Jul 22, 2020 at 12:36 AM Marco Atzeri via Cygwin wrote: > On 22.07.2020 02:10, Tony Richardson via Cygwin wrote: > > I have attached both the cygcheck and strace output. > > > > Tony Richardson > > > > something is clearly interfering with your Cygwin installation > > --- Process 11136 loaded C:\Applications\cygwin64\bin\cygwin1.dll at > 00c8 > --- Process 11136 unloaded DLL at 00c8 > I only appear to have problems with graph. Everything else seems to work fine. Tony -- Problem reports: https://cygwin.com/problems.html FAQ: https://cygwin.com/faq/ Documentation:https://cygwin.com/docs.html Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple
xterm stackdump
Lately I have been experiencing an xterm stackdump with varying triggers but all leading to a forced exit. Here is typical output. Exception: STATUS_INTEGER_DIVIDE_BY_ZERO at eip=0045D5EF eax=0092 ebx=80080300 ecx= edx= esi=800D4C88 edi= ebp=0004 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. -- Problem reports: https://cygwin.com/problems.html FAQ: https://cygwin.com/faq/ Documentation:https://cygwin.com/docs.html Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple
[ANNOUNCEMENT] freetype2 2.10.2-2
The following packages have been uploaded to the Cygwin distribution: * freetype2-demos-2.10.2-2 * libfreetype6-2.10.2-2 * libfreetype-devel-2.10.2-2 * libfreetype-doc-2.10.2-2 FreeType 2 is a software font engine that is designed to be small, efficient, and highly customizable while capable of producing high-quality output (glyph images). This is a a rebuild of the 2.10.2-1 packages, with /usr/bin/freetype-config added to libfreetype-devel. That script is deprecated and is not included by default, but some apps still expect to find it. Ken Brown Cygwin's freetype2 maintainer -- Problem reports: https://cygwin.com/problems.html FAQ: https://cygwin.com/faq/ Documentation:https://cygwin.com/docs.html Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple
Re: graph (plotutils) seg-faulting
On 7/22/2020 1:36 AM, Marco Atzeri via Cygwin wrote: On 22.07.2020 02:10, Tony Richardson via Cygwin wrote: I have attached both the cygcheck and strace output. Tony Richardson something is clearly interfering with your Cygwin installation --- Process 11136 loaded C:\Applications\cygwin64\bin\cygwin1.dll at 00c8 --- Process 11136 unloaded DLL at 00c8 I can reproduce the problem on my system: $ strace graph --- Process 30536 created --- Process 30536 loaded C:\Windows\System32\ntdll.dll at 7ff82a4c --- Process 30536 loaded C:\Windows\System32\kernel32.dll at 7ff8289c --- Process 30536 loaded C:\Windows\System32\KernelBase.dll at 7ff8280c --- Process 30536 thread 14832 created --- Process 30536 thread 31180 created --- Process 30536 loaded C:\cygwin64\bin\cygplot-2.dll at 00bc --- Process 30536 unloaded DLL at 00bc --- Process 30536 loaded C:\cygwin64\bin\cygwin1.dll at 00bc --- Process 30536 unloaded DLL at 00bc [...] --- Process 30536 loaded C:\cygwin64\bin\cygiconv-2.dll at 0178 --- Process 30536 unloaded DLL at 0178 [...] --- Process 30536 exited with status 0xc005 Segmentation fault I thought that simply rebuilding plotutils might fix the problem, but there were a lot of compilation warnings, and the build failed. Some of the warnings look serious to me, but I have no idea if they could cause Windows to try to load DLLs at strange addresses. Ken -- Problem reports: https://cygwin.com/problems.html FAQ: https://cygwin.com/faq/ Documentation:https://cygwin.com/docs.html Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple
