windbg-extensions | Various extensions for WinDbg

by goldshtn C Version: Current License: Apache-2.0

X-Ray Key Features Code Snippets Community Discussions(3)Vulnerabilities Install Support

kandi X-RAY | windbg-extensions Summary

windbg-extensions is a C library. windbg-extensions has no bugs, it has no vulnerabilities, it has a Permissive License and it has low support. You can download it from GitHub.

A WinDbg extension that supports open/close tracing for arbitrary objects. For example, it can be used to find memory leaks (memory that is allocated and not freed), socket leaks, and other kinds of unbalanced resources.

Support

Quality

Security

License

Reuse

Support

windbg-extensions has a low active ecosystem.

It has 149 star(s) with 39 fork(s). There are 26 watchers for this library.

It had no major release in the last 6 months.

There are 1 open issues and 1 have been closed. On average issues are closed in 5 days. There are no pull requests.

It has a neutral sentiment in the developer community.

The latest version of windbg-extensions is current.

Quality

windbg-extensions has no bugs reported.

Security

windbg-extensions has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.

License

windbg-extensions is licensed under the Apache-2.0 License. This license is Permissive.

Permissive licenses have the least restrictions, and you can use them in most projects.

Reuse

windbg-extensions releases are not available. You will need to build from source code and install.

Installation instructions are not available. Examples and code snippets are available.

Top functions reviewed by kandi - BETA

kandi's functional review helps you automatically verify the functionalities of the libraries and avoid rework.
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of windbg-extensions

Get all kandi verified functions for this library.

windbg-extensions Key Features

No Key Features are available at this moment for windbg-extensions.

windbg-extensions Examples and Code Snippets

No Code Snippets are available at this moment for windbg-extensions.

Community Discussions

Trending Discussions on windbg-extensions

WinDbg extension not recognizing command

Increase PYKD heap_stat performance, disabling RtlValidSecurityDescriptor

How to get variable names out of a dump and a symbol file?

QUESTION

WinDbg extension not recognizing command

Asked 2020-May-28 at 21:11

I am trying to write a WinDbg extension command and running into some problems. I started with this project and tried to modify it to supply a custom command in the debugger.

However when I run TestCommand I get the following error.

The command was: !TestCommand this is a test0:000> !TestCommand this is a test No export TestCommand found

The full code I have is below. I have attempted adding the [Export] modifier to the TestCommand function however this has not rectified the situation. How would I get WinDbg to recognize the command?

Full extension code:

...

ANSWER

Answered 2020-May-28 at 21:11

I think there's a misunderstanding. OnCommandExecuted() is an event listener which invoked when you entered a command in WinDbg. The given UI extension you have compiled will first be notified about the command, then WinDbg will try and actually run the command. Since the command does not exist, it will respond with the same error message that you get when no UI extension is loaded.

If I understand correctly what you want, then you're trying to implement a WinDbg extension (not a UI extension) that implements the command !TestCommand. That's usually a totally different approach.

In the given source code, you find a "regular" WinDbg extension in the WinDbgScriptRunner.x64 and WinDbgScriptRunner.x86 projects. There you can see that you need

Source https://stackoverflow.com/questions/61991901

QUESTION

Increase PYKD heap_stat performance, disabling RtlValidSecurityDescriptor

Asked 2019-Jan-09 at 19:49

While working with heap_stat (a Python script based on PYKD library for running Python scripts in a Windbg environment), I'm getting frustrated by the enormous time this script needs for doing its job.

So, I've started a profiling session, using "Very Sleepy", and this gave following result:

...

ANSWER

Answered 2019-Jan-09 at 13:33

I saw your xperf log anf here you are results:

25% CPU got call heap_output = dbgCommand('!heap -h 0').split('\n')

75% loop for heap_block in heap_output: and the main CPU consumer is pykd.ptrPtr

The main cause of CPU loss is massive calling dbgeng!FlushCallbacks internally by Debug Engine. In Fact, all Debug Engine funciton recall this method and I don't understand why.

I can advice you to have refactored heap_stat.py and rewrite your own ptrPtr funciton with ptrDword or ptrQword, it may decrease CPU losses.

Source https://stackoverflow.com/questions/54077490

QUESTION

How to get variable names out of a dump and a symbol file?

Asked 2017-Dec-13 at 00:25

I'm debugging dump files, while I have access to the symbol files.

I'm using a script, which combines the results of following windbg commands:

...

ANSWER

Answered 2017-Dec-13 at 00:25

I wrote the following MFC application (partial source):

Source https://stackoverflow.com/questions/47750504

Community Discussions, Code Snippets contain sources that include Stack Exchange Network

Vulnerabilities

No vulnerabilities reported

Install windbg-extensions

You can download it from GitHub.

Support

For any new features, suggestions and bugs create an issue on GitHub. If you have any questions check and ask questions on community page Stack Overflow .

Find more information at: