Merge content from report-a-problem-minidumps page with report-a-problem-perfview page (#8826)

* Merging creating minidumps content with ETL trace page

* Update headings

* fix for review comment

* fix for review comments

Author: anandmeg

.openpublishing.redirection.json

@@ -90,6 +90,16 @@
       "redirect_url": "/visualstudio/ide/how-to-report-a-problem-with-visual-studio",
       "redirect_document_id": false
     },
+    {
+      "source_path": "docs/ide/report-a-problem-minidumps.md",
+      "redirect_url": "/visualstudio/ide/report-a-problem-perfview-minidumps",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "docs/ide/report-a-problem-perfview.md",
+      "redirect_url": "/visualstudio/ide/report-a-problem-perfview-minidumps",
+      "redirect_document_id": true
+    },
     {
       "source_path": "docs/data-tools/additional-resources-for-troubleshooting-data-access-errors.md",
       "redirect_url": "/answers/products/?WT.mc_id=msdnredirect-web-msdn",

docs/ide/report-a-problem-minidumps.md

@@ -0,0 +1,71 @@
+---
+description: "PerfView is a tool that creates ETL (event trace log) files based on Event Tracing for Windows) that can be useful in troubleshooting some kinds of issues with Visual Studio."
+title: Collect an ETL trace with PerfView and create minidumps with all call stacks
+ms.date: 10/11/2021
+ms.topic: how-to
+helpviewer_keywords:
+  - "perfview"
+  - "ETL Trace"
+  - minidumps for Visual Studio issues"
+author: corob-msft
+ms.author: corob
+manager: jmartens
+ms.technology: vs-ide-general
+dev_langs:
+ - CSharp
+ - VB
+ - CPP
+ms.workload:
+  - "multiple"
+ms.description: "Collect ETL traces using perfview.exe and create minidumps to send to Microsoft, for troubleshooting issues with Visual Studio"
+---
+# Collect an ETL trace with PerfView and create minidumps with all call stacks
+
+When you report a problem with Visual Studio, the Microsoft product team might ask for an ETL trace or minidumps to collect additional information for troubleshooting. Use the following steps to collect an ETL trace or to create minidumps for all call stacks.
+
+## Collect an ETL trace with PerfView
+
+PerfView is a tool that creates ETL (event trace log) files based on [Event Tracing for Windows](/windows/desktop/ETW/event-tracing-portal) that can be useful in troubleshooting some kinds of issues with Visual Studio. Occasionally when you report a problem, the product team might ask you to run PerfView to collect additional information.
+
+### Install PerfView
+
+Download PerfView from [GitHub](https://github.com/Microsoft/perfview/blob/master/documentation/Downloading.md).
+
+### Run PerfView
+
+1. Right-click on **PerfView.exe** in Windows Explorer and choose **Run as administrator** as admin.
+1. On the Collect menu, choose **Collect**.
+1. Check **Zip**, **Merge**, and **ThreadTime**.
+1. Increase **Circular MB** to 1000.
+1. Change **Current Dir** to save ETL traces to a specified folder and Data File if you are going to collect more than once.
+1. To start recording data, choose the **Start Collection** button.
+1. To stop recording data, choose the **Stop Collection** button. The PrefView.etl.zip file will be saved in the specified directory.
+
+PerfView can store only the most recent data that fits into its buffer. Therefore, try to stop the collection as soon as possible after Visual Studio starts to freeze or slow down. Don't collect for more than 30 seconds after you hit a problem.
+
+For more information, see [PerfView Tutorial on Channel9](https://channel9.msdn.com/Series/PerfView-Tutorial/PerfView-Tutorial-1-Collecting-data-with-the-Run-command).
+
+## Create minidumps for a Visual Studio process with all call stacks
+
+In some cases, Microsoft might ask for a minidump of a running Visual Studio process with information for all call stacks. To collect this information, perform these steps:
+
+### Create the minidump file
+
+1. Start a new instance of Visual Studio.
+1. From the main menu, choose **Debug** > **Attach To Process**.
+1. Check the relevant **Managed** and **Native** check boxes and press **Attach**.
+
+   ![Attach to process](../ide/media/attach-to-process.png)
+
+1. Select the other Visual Studio instance to attach to from the list of running processes.
+1. From the main menu, choose **Debug** > **Break All**.
+1. From the main menu, choose **Debug** > **Save Dump As**.
+
+### Get the call stacks from the minidump
+
+1. Open the dump file in Visual Studio.
+1. Go to **Tools** > **Options** > **Debugging** > **Symbols** and make sure that **Microsoft Symbol Servers** is checked in the **Symbol file (.pdb) locations**.
+1. Open the **Command** window (**View** > **Other Windows** > **Command Window**).
+1. Type ‘~*k’. The window displays all threads' call stacks.
+1. Copy all text from Command Window and save to a text file.
+1. Attach the txt file to the bug.

docs/ide/report-a-problem-perfview-minidumps.md

@@ -1468,12 +1468,10 @@
       href: ide/how-to-report-a-problem-with-visual-studio.md
     - name: Get performance issues fixed quicker
       href: ide/how-to-increase-chances-of-performance-issue-being-fixed.md
-    - name: Create minidumps with callstacks
-      href: ide/report-a-problem-minidumps.md
     - name: Create logs for MSBuild problems
       href: ide/msbuild-logs.md
-    - name: Collect an ETL trace with PerfView
-      href: ide/report-a-problem-perfview.md
+    - name: Collect an ETL trace and create minidumps
+      href: ide/report-a-problem-perfview-minidumps.md
   - name: Suggest a feature
     href: ide/suggest-a-feature.md
   - name: Developer Community guidelines