All geek questions in one place

Production debugging: is there a less intrusive way than WinDbg?

I was wondering if there is a less intrusive way to analyze a running process in production environments.

Less intrusive value:

  • No delay when installing the debugger.
  • No execution delay when receiving basic statistics, for example, when starting threads.

In the Java world there is such an instrumental part of the JDK. I was wondering if there are similar tools in the .NET world.

The tool should answer questions such as:

  • What are the thread pool options? Same as "! Threadpool" in Windbg.
  • What are the calls of my current running threads (yes, you get this from the Java tool :)).
  • Core heap analysis, for example. how many objects like ABC.

Any ideas?

Alex

+3
4

, , . Process Explorer.

+2

Oefe, , Process Explorer. , .NET , . , .

+1

, ETW

+1

, . WinDbg - Windows, - .

If you just want to debug a program, most people just use a visual studio that will attach to running processes.

However, @oefe may have a bull by the horns here. When most people say "debugger", they need backtracks and breakpoints, etc. In Java, you need to make preliminary agreements for connecting such a debugger. Either Windbg or a visual studio (-debugexe) is more convenient than that.

0
source

Source: https://habr.com/ru/post/1736785/

More articles:


All Articles