-
hi,
I just tried the debugger, it start's successfully, and support step execution very well. also I can see local vars.
But I can't see the println 's output result.
so , what's the problem?
-
OS is Windows, region is India, language is English, US. Computer is a Dell Inspiron laptop.
To heavily truncate the backstory, I'm working on a project that requires the creation of a latin font wit…
NoSJW updated
3 years ago
-
Currently it is possible to scan memory only by dumping it manually to a file and using the ```--raw``` option. A useful feature would be the ability to parse core dump files (gdb can generate core du…
-
With the current anti-cheat update the project is unusable for a number of reasons. Most importantly, the anti-cheat is preventing debugger attaching, IDA de-compiling, and any other process that'd re…
-
With
```
dx -r1 Debugger.State.FunctionAliases
```
I get
```
dflow [!dflow []
Shows the instructions of the function containing [] which influence the source operands of that ins…
-
Hi Anton! Why don't you use boost/config/auto_link.hpp to avoid manual linking for VS when one of the link macroses is defined?
-
The long-name DAC is not needed at runtime. As part of our contract with WinDBG, we need to upload CoreCLR and the DAC together in a package so they can be indexed by the symbol server. If possible, w…
-
To be really useful, we need to be able to attach to a new process being created, and break on the entrypoint.
This address should be in the `Win32StartAddress` field of the `ETHREAD`.
with the …
-
Currently we support X64 and X86 Windows hosted Debugging Services Binaries for debugging Linux core dumps. This means that an x86/x64 Visual Studio or Windbg debugger (running on Windows) is needed …
-
After merging this [PR](https://github.com/dotnet/runtime/pull/2107), we will obtain some improvements debugging optimized code. It would be great to have checks we can run on every new PR to be sure …