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.
Related
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.
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 was looking for a debugger for Windows, other than GDB, which is freely accessible. I found WinDbg and it looks quite good so I wanted to give it a try. Now when I go to the MSDN page it offers to download the SDK for Windows 8. As this is a rather big package, I wonder if I can use this WinDbg version still for Windows XP?
Since my company still uses Windows XP for some time to come, I'm stuck with it for now. Is there another, free debugger which is user friendly?
I'm used to Visual Studio for debugging, which is quite nice. Currently I use Eclipse with GCC and GDB. GDB is good enough, but when I do some assembly I don't really like it, and all in all I don't find it very user friendly.
The latest WinDbg will work with Windows 2000 onwards and most commands work with Windows XP. There will be some that will only work with later versions, but these are documented in the included help file.
Just to ease your download pain, firstly there is the option to select what to download from MSDN, or you can just download the version you want here thanks to a kind person who is hosting the individual components.
What's missing in dbgeng.dll in windows 7 Vs the dbgeng.dll distributed with debugging tools for windows ?
Very late to the party on this one but I've run into one very significant difference recently:
The dbgeng.dll built into windows installations will not support remote debugging where as the one installed with debugging tools does!
There appear to be other differences also that I didn't dig deeper into - all I knew was a working program using the built in dll started crashing when using the debugging tools one... which was a pain considering I would have liked to use the remote debugging facility out of the box.
This post shows the difference between Windows 7 and Windows 8 preview, I believe Windows 8 version is similar or possibly same as latest one that ships that is in debugging tools because when I do use dependencyWalker I notice that the one in Debugging Tools also has this new exported method DebugCreateEx which is also in the latest version
Windows 7 System 32 version:
Dependency walker:
Debugging tools version:
Dependency walker:
Hope this helps in some way to explain the differences, especially the post at the top.
I want to test my web application on Internet Explorer 9 but I don't want to buy a copy of Vista/Win 7 on my developer machine with Windows XP.
Anyone knows a workaround, free and easy?
Use another machine.
Or better, get a set of Virtual Machines established which have an array of operating systems and browsers installed. Build enough VMs, and you are covered for all eventualities, regardless of whether you would personally use them or not.
Link to Internet Explorer Application Compatibility VirtualPC Images
You can't. The closest you'll get is IE9Preview.
I've found that IETester is not a bad way to quickly switch between browser versions for testing.
http://wiki.winehq.org/WineOnWindows
You can try running Wine on windows.
This will let you emulate a newer version of Windows
However, it will be really buggy (not mentioning how Wine is already buggy)
Its a unix/linux application ported for Windows
:)
IE 7,8,9
https://browserlab.adobe.com
Use
https://browserling.com
In unpaid version you have 3 minutes to test any site accessed from Internet on any browser.
In paid version you have unlimited sessions and ssh tunneling.