Re: "/usr/bin/tar.exe" hangs, Windows 10, CYGWIN_NT-10.0 3.0.7(0.338/5/3) 2019-04-30 18:08 x86_64
Keith Christian writes: > This is a corporate PC so little chance of doing any uninstalls or > modification. At least I know why now, and you've given me some ideas > about troublesome DLL's. Been there, done that. Usually Symantec Endpoint Protection does come with a support contract and Symantec support definitely knows about Cygwin even when your IT folks don't. So open ticket, support request or whatever they call it with your IT and insist they escalate to Symantec if they can't solve your problem (e.g. by excluding the Cygwin install directory from heuristic checks). The problem may return after some updates or whenever someone feels that your company devices need "extra" protection. Sometimes it helps to do a full scan on the Cygwin install directory, as some of the more problematic heuristics are skipped when the scanner has seen and whitelisted a file before. Regards, Achim. -- +<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+ SD adaptation for Waldorf microQ V2.22R2: http://Synth.Stromeko.net/Downloads.html#WaldorfSDada -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: XWin can't hold OpenGL picture, has WS_DISABLED and WS_EX_TRANSPARENT styles?
I've put forward a patch (https://sourceware.org/bugzilla/show_bug.cgi?id=25170) to this for anyone interested. I'll explore putting it elsewhere, but I really think these mailing lists are an albatross, not sure I want to join another. - Original Message - > From: "Mick Pearson" > To: "cygwin" > Sent: Wednesday, November 13, 2019 1:27:53 AM > Subject: Re: XWin can't hold OpenGL picture, has WS_DISABLED and > WS_EX_TRANSPARENT styles? > Sorry (I don't know how to you L A Walsh reply so am replying to myself with > the > same subject) > I think I meant to include this > (https://sourceware.org/bugzilla/show_bug.cgi?id=25170) link that > includes this link: > > https://www.mail-archive.com/search?l=cygwin-xf...@cygwin.com&q=subject:"Re\%3A+Probable+bug+in+WGL+implementation+\(AIGLX\)+of+GLX+calls+in+XWin+\-wgl"&o=newest&f=1 > > I was too zealous to be brief, and I think now the window styles are a red > herring. In any case the > problems arise in "overdraw" scenarios wherein a window passes over the OpenGL > windows, that > is when the background is "erased" and the picture is lose (not held) which > makes it impossible to > use XWin for anything but one screen demonstrations of graphical effects. Some > applications use > multiple windows and do rendering with OpenGL instead of GTK widgets for > example. Those can't > use XWin. I think OpenGL doesn't work with MS Windows X servers. I hope it > works > with Linux ones. > > The other X servers available to Windows are in disarray with regard to > OpenGL. > So it would be good > if one of them could be made to work. XWin is closest since it doesn't crash > and > does draw correctly > other than it can't hold a picture. > > - Original Message - >> From: "Mick Pearson" >> To: "cygwin" >> Sent: Saturday, November 9, 2019 3:49:12 AM >> Subject: Re: XWin can't hold OpenGL picture, has WS_DISABLED and >> WS_EX_TRANSPARENT styles? > >> P.S. Sorry to add, the WM_ERASEBKGND message occurred to me, or setting the >> class-background to the "null" brush is a likely culprit. It is behaving like >> a front-buffered old-fashioned application somewhat. Clipping and own-DC >> style >> should prevent damage, but I don't know, something seems to be responding to >> PAINT like events, that don't make sense for OpenGL. >> >> Below is line formatted version of the old text. I have to do this manually >> for >> new text, but the > quoted text is already hard-wrapped. >> >>> XWin has never had a permanent picture with OpenGL. Any movement "damages" >>> all >>> windows. I know I've looked at it before, but I checked its window/class >>> styles >>> with MS's Spy++ tool today. The normal styles that govern clipping and >>> permanence look fine, but it has some weird styles that normally for >>> disabled >>> and transparent windows that I wonder are the cause for its abnormal >>> behavior >>> in this regard. No OpenGL apps that just draw only OpenGL on a window have >>> XWin's problem. >>> >>> To be brief, it has these unnatural window-styles in this mail's subject >>> line. >>> Other than that, I think it may use Direct3D instead of OpenGL, but normally >>> drawing OpenGL or Direct3D onto plain windows doesn't clobber other >>> windows. I >>> mean, you have to work hard to make it do something like that. >>> >>> A second, unrelated, oddity is the window decorations are sometimes classic >>> style, and sometimes current style. It's very odd. It's random in the same >>> session. The windows seem to undergo a transition from classic to current, >>> but >>> get stuck in classic sometimes. Maybe they are using the old "animated" show >>> functions that didn't survive the version of Windows that introduced them. >>> >>> Niggling things like this could be fixed. But I don't know how many people >>> use >>> Cygwin. I've used it a lot over the years myself, to do development work. >>> XWin >>> is the most stable X server. Others don't really get close. But it's kind of >>> too comfortable with its crumminess too. Not that I'm going to shove my work >>> aside to try to remedy it myself. >>> >>> -- >>> As with mail, anyone who wishes may send email from your email address. In >>> the >>> case you receive obscene or unusual email from an address with which you are >>> familiar. It could be someone is impersonating that email address. Always >>> return a copy of the email to the sender for review and response. >> >> -- >> As with mail, anyone who wishes may send email from your email address. In >> the >> case you receive obscene or unusual email from an address with which you are >> familiar. It could be someone is impersonating that email address. Always >> return a copy of the email to the sender for review and response. > > -- > As with mail, anyone who wishes may send email from your email address. In the > case you receive obscene or unusual email from an address with which you are > familiar. It could be someone is impersonating that e
Re: XWin can't hold OpenGL picture, has WS_DISABLED and WS_EX_TRANSPARENT styles?
On 2019-11-16 06:39, Mick Pearson wrote: > On Wednesday, November 13, 2019 1:27:53 AM, Mick Pearson wrote: >> On Saturday, November 9, 2019 3:49:12 AM, Mick Pearson wrote: XWin has never had a permanent picture with OpenGL. Any movement "damages" all windows. I know I've looked at it before, but I checked its window/class styles with MS's Spy++ tool today. The normal styles that govern clipping and permanence look fine, but it has some weird styles that normally for disabled and transparent windows that I wonder are the cause for its abnormal behavior in this regard. No OpenGL apps that just draw only OpenGL on a window have XWin's problem. To be brief, it has these unnatural window-styles in this mail's subject line. Other than that, I think it may use Direct3D instead of OpenGL, but normally drawing OpenGL or Direct3D onto plain windows doesn't clobber other windows. I mean, you have to work hard to make it do something like that. A second, unrelated, oddity is the window decorations are sometimes classic style, and sometimes current style. It's very odd. It's random in the same session. The windows seem to undergo a transition from classic to current, but get stuck in classic sometimes. Maybe they are using the old "animated" show functions that didn't survive the version of Windows that introduced them. Niggling things like this could be fixed. But I don't know how many people use Cygwin. I've used it a lot over the years myself, to do development work. XWin is the most stable X server. Others don't really get close. But it's kind of too comfortable with its crumminess too. Not that I'm going to shove my work aside to try to remedy it myself. >>> WS_EX_TRANSPARENT styles? >>> P.S. Sorry to add, the WM_ERASEBKGND message occurred to me, or setting >>> the class-background to the "null" brush is a likely culprit. It is >>> behaving like a front-buffered old-fashioned application somewhat. >>> Clipping and own-DC style should prevent damage, but I don't know, >>> something seems to be responding to PAINT like events, that don't make >>> sense for OpenGL. >> I think I meant to include this>> >> (https://sourceware.org/bugzilla/show_bug.cgi?id=25170) link that includes >> this link:>> >> https://www.mail-archive.com/search?l=cygwin-xf...@cygwin.com&q=subject:"Re\%3A+Probable+bug+in+WGL+implementation+\(AIGLX\)+of+GLX+calls+in+XWin+\-wgl"&o=newest&f=1 >> >> I was too zealous to be brief, and I think now the window styles are a red >> herring. In any case the problems arise in "overdraw" scenarios wherein a >> window passes over the OpenGL windows, that is when the background is >> "erased" and the picture is lose (not held) which makes it impossible to >> use XWin for anything but one screen demonstrations of graphical effects.>> >> Some applications use multiple windows and do rendering with OpenGL instead >> of GTK widgets for example. Those can't use XWin. I think OpenGL doesn't >> work with MS Windows X servers. I hope it works with Linux ones.>> >> The other X servers available to Windows are in disarray with regard to >> OpenGL.>> So it would be good if one of them could be made to work. XWin is >> closest >> since it doesn't crash and does draw correctly other than it can't hold a >> picture. > I've put forward a patch > (https://sourceware.org/bugzilla/show_bug.cgi?id=25170) to this for anyone > interested. I'll explore putting it elsewhere, but I really think these > mailing lists are an albatross, not sure I want to join another. As everyone is a volunteer with little free time, Cygwin no longer uses sourceware/bugzilla, it uses mailing lists and git format-patch/send-email patches, to make it quick and easy for committers to apply with git am. Please submit app patches to cygwin-a...@cygwin.com in git format-patch/send-email format (with --cover-letter if a patch series). -- Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada This email may be disturbing to some readers as it contains too much technical detail. Reader discretion is advised. -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: "/usr/bin/tar.exe" hangs, Windows 10, CYGWIN_NT-10.0 3.0.7(0.338/5/3) 2019-04-30 18:08 x86_64
On 2019-11-16 03:48, ASSI wrote: > Keith Christian writes: >> This is a corporate PC so little chance of doing any uninstalls or >> modification. At least I know why now, and you've given me some ideas >> about troublesome DLL's. > > Been there, done that. Usually Symantec Endpoint Protection does come > with a support contract and Symantec support definitely knows about > Cygwin even when your IT folks don't. So open ticket, support request > or whatever they call it with your IT and insist they escalate to > Symantec if they can't solve your problem (e.g. by excluding the Cygwin > install directory from heuristic checks). The problem may return after > some updates or whenever someone feels that your company devices need > "extra" protection. Sometimes it helps to do a full scan on the Cygwin > install directory, as some of the more problematic heuristics are > skipped when the scanner has seen and whitelisted a file before. I've been "official" Cygwin app installer/maintainer at a couple of gigs, where jumping thru the /virtual/ hoops to add Cygwin to the app catalog and assign it to myself, was easier than asking or getting permission to install or use it. Jumping thru the /virtual/ hoops to raise an issue can often prevent all future issues: reference https://support.symantec.com/us/en/article.HOWTO80920.html#v72437653 -- Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada This email may be disturbing to some readers as it contains too much technical detail. Reader discretion is advised. -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: linker fails with multiple definitions after inline thread_local var within class
OTOH: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64697#c20 Thank you again. On looking harder on gcc bugzilla I found a related case from mid 2017 that had not been looked at yet, so I have tried adding my report to that. And meanwhile in my own code I am using work-arounds! The prompt responses from you when you have so many postings to the list is good to see. Arthur -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
