New answers tagged debuggers
0
I needed to put the cursor within the disassembly view (not HEX view), right-click on the disassembly view and then check the option again, it should be available.
This answer help me.
Another thing,
You can't trace if the instruction has breakpoint. You need to remove the breakpoint and then assign the trace.
If you set a function to be traced, and it doesn'...
0
You Cannot use contains for objects they are not strings
contains only is meaningful when you have a partial case Sensitive pattern
here is how you may use contains
0: kd> dx Debugger.Sessions.First().Processes.Where(p=>p.Name.Contains("Taskm"))
Debugger.Sessions.First().Processes.Where(p=>p.Name.Contains("Taskm"))
[0x2c14] ...
1
Here is how to do it:
dx @$cursession.Processes.Where(p => p.Environment.EnvironmentBlock.ProcessParameters->CommandLine->ToDisplayString().Contains("chrome"))
If you have other way, please share.
1
maybe try : C:\Program Files (x86)\Windows Kits\10\Debuggers\x86
0
After I ran:
0: kd> .symfix C:\debug\symbols
*** Unable to resolve unqualified symbol in Bp expression 'user32.SetWindowTextW'.
*** Unable to resolve unqualified symbol in Bp expression 'user32.SetWindowTextW'.
0: kd> !sym noisy
noisy mode - symbol prompts on
0: kd> .reload /f
Now I was able to use it:
0: kd> dd user32!SetWindowTextW
00007ffc`...
0
After the steps mentioned by @GameMaster Greatee look under the "Plugins" menu in the main x64dbg window or in the secondary menu in the Disasm window as well for an "xAnalyzer" entry.
Source:https://github.com/ThunderCls/xAnalyzer
Top 50 recent answers are included
