I have installed Gnuplot on a new Windows laptop, with all of the Windows updates applied and I am finding that Gnuplot is working fine in interactive mode but when I pipe data to it the graphs plot but I can't interact with the graphs via the mouse becasue the window freezes and says "Not Responding".
Interestingly, I can continue to pipe data to Gnuplot and the graphs are all plotted correctly.
I've tried 5.2.8 and 5.4.1 and I do not have any problems with either, on my old laptop with all the same Windows updates.
I'm at a loss! and wondering if it is somehow related to Microsoft anti-virus, anti-malware etc. I've tried disabling all of these but makes no difference.
I'm hoping that someone here might be able to give me some suggestions to try.
Thanks very much, as always,
John
This is a known problem under Windows 10. As best as I can determine from the bug reports on the gnuplot issue tracker, the problem is specific to gnuplot 5.4 + Windows 10. One reporter suggests that reversion of commit 651af626 would fix the problem (at the cost of significant slowdown), but I have not seen confirmation of this by other testers. If you can build from source and confirm that fix it would be a great help.
See https://sourceforge.net/p/gnuplot/bugs/2412/
Related
UPDATE
This question seeks help with tooling - "how do I debug my problem." As I type this, there has been no answers. I did end up stumbling on the solution for the actual problem I was trying to solve and have provided the solution as an answer.
I still would be more than happy to hear any answers on the tooling question though, and if somebody comes up with a workable answer, I'll be more than happy to transfer the checkmark
Original Question
I initially opened an issue with YouCompleteMe https://github.com/Valloric/YouCompleteMe at https://github.com/Valloric/YouCompleteMe/issues/1345. It immediately got closed because there's no official support for Windows. Ok, fine.
I'm now asking the Stackoverflow community, hopefully there are people who are messing with YCM for Windows (there is a "unofficial YCM for Windows" page, so there MUST be SOMEBODY hacking on this thing).
Below is the original content of the issue that I opened.
If somebody actually has an answer that works, great! At this point, I'm looking more for procedures that I can use to run the YCM server under a debugger to see where exactly it's choking
I'm trying to get YCM to work on my Windows 7 machine. I have a few
other XP, Win7, Win8 machines that have no problems with YCM. I've
tried building the support stuff using MinGW, Visual Studio 2010, both
on the target machine as well as the other machines where I have YCM
working.
When I open a Python or C++ file, a message immediately appears that
YCM has crashed and I should restart with :YcmRestartServer. It
mentions that I should set g:ycm_server_keep_logfiles in order to see
the log messages. I have done that, but I still don't have any
logfiles and the "set g:ycm_server_keep_logfiles" message is still
appearing.
I also get ('Connection aborted.', error(10061, 'No connection could
be made because the target machine actively refused it'))
I looked in python\ycm\youcompleteme.py and saw that the "logfiles
deleted" message comes up because of an exception in trying to open
the file specified by self._server_stderr (IOError). Right now I'm
suspecting that this is because the server never actually gets far
enough in its startup sequence to actually create the stdout and
stderr files.
What are the steps that I could do to investigate why the server (?)
fails to start properly.
I also had a vague idea that there was a firewall rule blocking
connections, I looked through Windows Firewall, but didn't really see
anything that would point to localhost connections being blocked or
whatnot.
I'm okay with doing debugging, would appreciate advice on the
procedure that I would need to do in order to get Visual Studio 2010
to step into the server process and poke around stuff.
Oh, dunno if this factoid means anything, but I'm able to use
Rip-Rip's clang_complete without issues, but I would very much rather
use YCM.
I never really did get an answer or solution to the central question of "how do I debug YCM under Windows" but I did solve the underlying problem of why YCM wasn't working for me, so for posterity (and other fellow despairing YCM users who may end up here via Google)
For me, YCM immediately crashed and burned. I figured the problem out by seeing a Windows system that had been working fine for me start exhibiting the symptoms.
The change: I had installed Python 3.x and switched it to being the system preferred python (by messing with paths, what do you expect with Windows?).
As it turns out (duh), YCM depends on Python 2.x and falls over when it can't find any of the libraries that it was trying to open.
I started going down the path of trying to locate exactly what the files YCM was trying to access and provide them locally in the YCM directory, but after spending five minutes on it, I decided that I wanted something simpler.
Since I still wanted Python 3.x to be the 'system' version, I settled for manipulating the path WITHIN Vim, so I added this before the YCM load,
if (has('win32') || has('win64'))
let $PATH = 'C:\Python27;' . $PATH
endif
Hope that this saves somebody else some pain
I'm not sure if this is the right place to ask, seeing as I don't currently have any code to share, but perhaps someone has an insight.
I have a very old Flash MX projection (.exe file) that was written and compiled in flash MX 2004. It's a simple interactive app - a test where a user picks an answer to a question and pushes ENTER to move to the next question.
The projection works fine on WinXP SP3 but doesn't work in win7, failing with a "class not registered" error.
It does work after I install flash player activex (I tried installing the latest, and also legacy version 6 r71), but then it doesn't register any keyboard commands and crashes a short while after a key is pressed.
Any idea what can be causing this?
So far I've tried fiddling with IE security settings, disabling DWM and windows themes, compatibility settings, etc., with no luck.
Also, despite the fact that the compiled projection is supposed to have all necessary components to run inside, it doesn't run if flash.ocx isn't registered. Isn't that weird?
Any help will be appreciated. I know this is old stuff and no one promises compatibility etc. And I don't even have the code as of now (not sure I can find it; assume I can't) - but this app is somewhat important to my company and this really seems like a "small" issue - if I could just find it...
Update - it kinda works if install the latest flash player and run it in compatibility mode - but it hangs after about a minute, regardless of what i do.
if i run it without compatibility mode, it doesn't run with a "library not registered" error.
You might want to repackage it.
Extract SWF from projector executable, for example, using this tool.
Get the newest standalone Flash Player and check if your .swf-file works with it.
Now export new projector file.
If this doesn't work for you, the only other way to do this is to recompile your .swf from source.
I agree with Ale's solution.
Have you tried Window's compatibility options to run the .exe as it would in an older compatibility mode ? This may work.
I have been searching for the answer for this for 2 days. We have an application that uses ReportViewer 9. However, clicking on the print button in IE10 causes the browser to stop working (with the "Debug" or "Close Program" buttons). Everything else seems to work fine.
We tried using ReportViewer 10 but we get the same issue.
We are using Visual Studio 2010, Windows 7, IE 10, and targeting .NET 4.0. The crashes happen in the IDE and through IIS.
EDIT: Things I Have Tried:
I have tried adding my website to Trusted Sites, lowered the security setting, and I think I've tried every possible combination of checkboxes in the "custom" security box.
I've tried enabling Protected Mode and Enhanced Protected Mode, with a variety of check box combinations from Custom security level that sounded promising.
I've tried forcing IE10 to run in 64-bit mode (including the tabs), but our app forces the tab to run in 32-bit anyway.
Someone suggested that it might be a Kill Bit issue, so I tried editing the registry to ignore kill bits just to see if it would work (it didn't).
Also, I'm pretty sure I've tried just about every permutation of all the variables I've already mentioned. (I'm a little burnt out at this point, so I might have missed 1 :S)
This thread seemed promising but I could not get it to work. It is talking about Win8 but I thought I might be able to apply them to my situation.
I found a suggestion changing the BuildProvider assembly to type="Microsoft.Reporting.RdlBuildProvider, Microsoft.ReportViewer.WEBFORMS ..." (instead of Common), but so far that is not working either.
Tried installing Report Viewer 11, and installing a very old version of our application. Both give me the same result.
Aha! OK, so it turns out that my issue is NOT with ReportViewer, but rather with RSClientPrint. Once I did a google search for that I quickly found that the answer is: Upgrade to Sql Server 2008 R2 SERVICE PACK 2.
The version of RsClientPrint you get with R2/SP2 is 10.50.4000, while the version I had was 10.50.1600.
In conclusion, it appears that RSClientPrint 10.50.1600 is NOT COMPATIBLE with IE10, but version 10.50.4000 IS.
I REALLY hope this helps someone else!!
I am trying to use the HP Fortify Static Code Analyzer to analyze security concerns in a large C application and I have run into various bugs in the software itself that I cannot seem to find any answers to anywhere on the Internet. I am using version 3.4 of the software and running it on a Linux x64 system.
The main bug that I am encountering that makes it very difficult to use this product at all is that in various different places in their Audit Workbench GUI the program will just close for no reason. An example is whenever a pop-up window shows asking you a question and your answer to the question is just to close the pop-up window by either clicking on the close button or the cancel button, the whole program ends instead of returning you back to where you were when you originally got the pop-up. Another example is when I try to open the Rules Editor, either for a new Rule Pack or an existing Rule Pack, the program opens up a progress window with a moving progress bar that sits there and moves for a while but when it is finished, instead of opening up the Rules Editor, the whole program just ends suddenly.
Has anyone out there seen behavior like this? If so, please let me know what I can do about it. Thank you.
I would highly recommend upgrading to the latest (4.10 at the time of this post) version. One thing you can do to help diagnose issues is to look at the log files. These are located in (by default) [user.home]/fortify/AWB-3.40/log.
Also, since you are using Linux 64bit, you will want to ensure that AWB isn't trying to access the 32bit JRE at any time. This can be accomplished by removing [fortify install root]/jre and renaming [fortify install root]/jre64 to [fortify install root]/jre. Some of the tools default to /jre and so you can run into issues on Linux 64bit.
We are trying to automate a build of one of our products which includes a step where it packages some things with WISE. At one point WISE pops up a window with a progress bar on it to show how it is doing. If one is connected to the machine with remote desktop the build works fine but if one is not connected the build stalls until you reconnect at which point the window opens and the build progresses. Does anybody know of a work around for this? Some way of tricking windows into believing that there is a desktop session connected?
Sorry for yet another guess - but I had a problem with a wise installer locking up. It was because WISE had installed a "font" and so broadcast a "system config changed" message. My DELL had a Dell utility running on it that had a message queue it wasn't reading from so the broadcast locked up the installer. WISE made a new version for me that did an async broadcast instead to fix the problem. It's possible that there's an app on your system that doesn't bother reading its msg queue when there is no desktop.
Finally the answer: check you have the latest patches for your WISE installer. In particular, look for patches that fix lock-ups related to the windowing system.
What version are you using? Looking at the feature set, it looks like their "std" version might be limited. Perhaps unattended installs require the Pro version?
That's just a guess....
Regardless, I wonder whether you could simply code up an auto-run task for the box that calls
CreateDesktop to pretend there's an interactive login?
I found a CreateDesktop example
that's about desktop switching, and an example about unattended installs -- you might be able to use one of them as a starting point to "fake out" WISE :)
It might be worth a try...