microsoft / smartdump Goto Github PK

SmartDump v1.12

New feature:

Support of capture .Net 6 dump and exceptions has been added.

SmartDump v1.10

New feature:

Now -v option can real-time display manage callstack when a .net exception is thrown. Moreover using function name as filter to capture memory dump is supported.

(NOTE: this feature is only available on 32bit version currently and hasn't been added into 64bit version.

SmartDump v1.09

New feature:

This build is pretty much a big milestone: now -v option can real-time display manage callstack when a .net exception is thrown. Moreover using function name as filter to capture memory dump is supported in this build.

(NOTE: this feature is only available on 32bit version currently and hasn't been added into 64bit version.

SmartDump v1.08

New feature:

Added -v option to display verbose output to list frames of managed callstack. Then we can utilize addresses from its output to set breakpoint with -a option. For example, a code entry address of a function can be used to dump its corresponding interested call:

            SmartDump.exe -p 4567 -n 20 -v

The frame output indicates the entry code address of the first managed call that threw the exception is 0x00007ffd`551f0eb0.

So we use address: 00007ffd`551f0eb0 as breakpoint to capture dump with -a option:

As we can see, 00007ffd`551f0eb0 is just the entry address of function: System.Data.SqlClient.SqlConnection.OnError

SmartDump v1.07

New feature:

• Add exception information and associate it with thread context on capturing exception dump files, e.g:

SmartDump v1.06

New feature:

Added -mn option to support capture mini dumps. For example, the following command captures 3 mini dump files for each of the 3 specified exception types: InvalidOperationException, SqlException and ServiceOperationsProviderException .

    SmartDump.exe -p 3328 -n 40 -de 3 -mn -f "InvalidOperationException|SqlException|ServiceOperationsProviderException"

SmartDump v1.05

This is the first official release which is no longer a beta version.

Bug fix in this build:

• Fixed a major problem that output within Kudu console doesn't get refreshed immediately. Now it's possible to real-time monitor exceptions in Kudu just like running inside an on-promise command line:

• Fixed a bug that sometimes an exception message is recognized as exception type by mistake.
• Further improved accuracy of capturing managed exceptions.
• Fixed a bug in 32bit version that same exception object gets captured for multiple times.

SmartDump v1.04 beta

Bug fix in this build:

• Fixed a bug that exception object's namespace may not be properly retrieved in 32bit version.
• Added support for pressing Ctrl+Break to detach from a process but this still doesn't work inside Kudu console ( just like Ctrl+C ).
• Code optimization .

SmartDump v1.03 beta

New feature:

• Added -de option support. In this 'Dump for each' mode, dumps will be captured for each of different exception types. Exception types already captured will be skipped until all exception types specified in filter strings have been captured - start another round.

Example:

In the following sample, SmartDump with -de switch will capture 3 dumps for SqlException, InvalidOperationException and ServiceOperationsProviderException one by one.

Bug fix in this build:

• Fixed a problem that some specific exception types defined in System.dll cannot be properly recognized in 64bit version.

SmartDump v1.02 beta

New feature:

• Added functionality to detect target process termination and stop capturing.

Bug fix in this build:

• Fixed the problem that filter strings and dump count didn't work well with unmanaged exceptions. Now native error codes in hex can be used to filter unmanaged exceptions, just like how filter works with managed exception:

SmartDump v1.01 beta

New feature:

• Added support of pressing Ctrl+C to detach from target process. However please note Kudu console has a known limitation that doesn't support Ctrl+C to exit processes. Only copy/paste Ctrl+C/Ctrl+V is supported in Kudu.

Sample output:

20:26:44 [Managed Exception] <System.NullReferenceException> Object reference not set to an instance of an object.
User pressed Ctrl+C. Detaching from target process: 306256.

Bug fix in this build:

• Fixed a problem that System.NullReferenceException caused by 0xc0000005 Access Violation needs to be processed specially.

SmartDump v1.00 beta

New feature:

Add -s option support.

 -s     Skip the first number of exceptions for dump capture. This option is useful when initial exceptions cannot reflect an actual issue.

Example:

• Skip the first 3 NullReferenceException. Capture a memory dump for the 4th one and specify output path to: c:\home\dump.

        SmartDump.exe -p 4567 -n 10 -f "NullReferenceException" -s 3 -d 1 -o c:\home\dump
  

Bug fix in this build:

1. Fixed a bug of -a option of 64bit version on displaying stacks.
2. Limited max stack length to 30 to avoid endless loop while capturing dumps of stack overflow.
3. Optimized the code to detect and display 64bit memory addresses.

SmartDump v0.99 alpha

New feature:

Add -fv option support.
-fv Exclude exceptions contain specified filter. Use '|' as delimiter for multiple strings.

Add multiple strings support for -f option.

Examples:

• Capture two dumps based on filtered strings of managed exceptions:
  SmartDump.exe -p 4567 -f "Object reference not set|ArgumentException" -n 10 -d 2

• Exclude exceptions contain specified filter string from output:
  SmartDump.exe -p 4567 -n 10 -fv "InvalidOperationException|FileNotFoundException"

Bug fix in this build:

1. Fixed a bug of string buffer exceeded while retrieving exception types.
2. Fixed a bug that namespace string incorrectly truncated in some specific case.

SmartDump v0.98 alpha

Recent improvements in this build:

1. Further optimized code of retrieving managed exceptions. Far more accurate than previous builds.
2. Fix two bugs that can lead to target process termination/crash.
3. Default number of exceptions is set to 5 now due to limitation of Kudu console.

SmartDump v0.97 x64 alpha

Recent improvements in this build:

1. Improved verification of user input parameters.
2. Simplified input parameter. Number of exception to be monitored is set to 20 now(previous is unlimited). No need to specify -n by default. Set -n to 0 means unlimited.
3. Further improved the ability to retrieve managed exception types.
4. VC runtime library is built-in included and compiled into this build to resolve missing dependency error.

SmartDump v0.95 x64 alpha

Recent improvements in this build:

1. 64bit process support is available now - SmartDump64.exe.
2. New parameter to control dump count has been added.
3. Resolved some user privilege issues on dump collection.
4. Fix of exception number doesn’t apply to unmanaged first chance exceptions.
5. Release build that no longer depends on Debug version of VC++ runtime library.

It would be nice to have a way to trigger memory dump collection when CPU hits certain treshold (for example 70%)

In case you find any problem on using SmartDump, please describe details here.

[Problem]: procdump cannot successfully capture .net core exceptions inside Azure Kudu console

Repro steps of Procdump (the last version 08/18/2021)

1. Create a new Function App on Azure portal
   

2. Create a new function with HTTP trigger template and leave all things as default
   

3. Open Kudu console and Process Explorer from Advanced tools
   

4. Find PID in Process Explorer.
   

5. Launch Procdump and attach to this PID
   
   

6. Submit some invalid JSON data to the Function App to generate some exceptions
   
   

7. None of exceptions are captured
   

8. If -g option is used, then all the exceptions are captured as generic CLR exception.
   

9. Compare it with the output of my tool which correctly displays the exceptions.