I'm running on Windows 10:
Processor Intel(R) Core(TM) i9-10900K CPU # 3.70GHz 3.70 GHz
Installed RAM 64.0 GB (63.8 GB usable) Device
ID A90B50D3-489B-4AE1-BB44-38804085FE3A Product
ID 00330-53385-62923-AAOEM System type 64-bit operating system,
x64-based processor
I have installed and tested Julia:
I downloaded the latest version of VS Code and tried my "Hello World" Julia script as follows:
As you can see a the bottom of the screen, it never runs the program.
It is stuck!
Any help or suggestions will be greatly appreciated.
Charles
It seems like many people seem to have this issue, but the VS Code devs claim the bug has been fixed. Is it possible you are using an old version of the Julia VS Code Extension? See this issue: https://github.com/julia-vscode/julia-vscode/issues/1780 for details.
I was able to replicate some similar behavior (albeit on a different OS) and filed an issue here: https://github.com/julia-vscode/julia-vscode/issues/2391
I suggest you do the same unless any of the fixes on the first issue linked above work for you.
Related
Whenever I launch Unity Editor, I always get multiple of the same error message in my console, and one NullReferenceException.
What are these and how can I fix them? I tried searching the web and didn't find anything. Can I safely ignore them?
My machine is decently powerful with 16 GB ram, i5 8th gen # 1.8 GHz. Not sure if my machine is just laggy or if these are legitimate errors.
I'm using Ubuntu 20.04 LTS.
Confirmed bug by Unity Editor developer - bug report already made. The problem has existed since version 2020.1.13f1.
Until it is fixed you could either ignore it or downgrade to Unity version 2020.1.12f1 (last version without the bug).
The version 2020.1.12f1 is no longer listed in UnityHub, although it is possible to download it from command line:
$ ./UnityHub.AppImage unityhub://2020.1.12f1/55b56f0a86e3
If you don't have UnityHub it can be downloaded here.
Relates to: post on unity forum.
Unity Editor dev here. This is a bug. Please report it using Help->Report a Bug. We've made some changes in the Linux editor recently, and this message is part of it. Not something you should normally see.
I am currently writing an OS based on ARMv8 processor. I want to find an emulator that acts like the processor so I can see my OS working or not and to check my work.
I am on windows 10. are there any emulators recommended ?
I searched SO but no answer. thanks.
Looks like QEMU version 2.1+ is what you want
the latest version of upstream QEMU (2.1) now includes full ARMv8 system emulation support. This means that users can use upstream QEMU to run a full 64-bit ARMv8-A kernel and filesystem, such as a 64-bit Ubuntu cloud image. This was no small endeavour as it involved emulating a completely new instruction set, exception model, CPU implementation, and more. The implementation was verified with a custom instruction verification tool (RISU) and was heavily reviewed upstream by an engaged and incredibly supportive upstream QEMU community.
source
My Bluestacsk2 installation does not pop-up after extracting. Just nothing happens after that window. I tried disabling antivirus programs and running it as administrator. My system fulfils the system requirements:
Windows 10 Pro, 4 GB Ram.
Version: BlueStacks2_native_8e68b6e001e5a05ff01c3f89c5790f9d
I also have the latest version of Directx and .NET framework. My graphic card is up to date and works very well.
This problem occurs only for the Bluestacks 2. I can setup the previous beta version. I tried both win7 and win10 versions for Bluestacks2 but they are not starting to install.
I figured out that I don't have enough space in C drive. But it was really annoying that Bluestacks does not warn me about this. I had several gigabytes in C, but I have been able to install it properly after I removed 10 gb of data from there. (I don't think you need to remove such big data)
I am having trouble with Gwan, I have used is successfully without hiccup on several machines but having trouble with my current machine CentOS 6.3 64bit Final, gwan version 3.12.26, glibc version 2.12 (stable) from gwan.
Whenever I try and start gwan ./gwan
It returns back with
Linking loan.c: failed to map segment from shared object: Operation not permitted
I have full root access, have made sure that all .so shared files are executable, and ensured that SELinux was OFF.
Anything you all can shed some light on would be great
There are stability issues on version 3.12.26 due to GLIBC wrappers and direct system calls. The issues are different on different OS/GLIBC that's why it's working on some machines and not working on others.
I will suggest to use 3.3 (If you have it) for now until version 4 is released.
Richard Heath, give the link to download 3.3 version! Why all advices about G-WAN so uninformative? It's all like bla bla bla. I explore the whole gwan.com website. Only link to download latest version!
We recently moved from Windows XP to Windows 7 and ever since the move I've found that I can't run the !dlk command from Sosex in WinDbg anymore, it simply runs forever. It used to be a handy way to catch deadlocks in our code.
Did something change in Sosex that I should know about?
We're on Windows 7 64 bit debugging a crash dump from a x86 process that ran on a Windows 7 64 bit machine.
In the meantime I can try and work through !syncblk, but !dlk was sooooo nice.
As Rockstart said in a comment, major performance improvements have been made to SOSEX in recent weeks. Please let us know if you continue to have difficulty with the latest version of SOSEX. You can also email the address listed in !sosex.help for support.