diff --git a/get-started/_common/components/_debugging_analyze.md b/get-started/_common/components/_debugging_analyze.md
index 3479b5f8..0d63f02d 100644
--- a/get-started/_common/components/_debugging_analyze.md
+++ b/get-started/_common/components/_debugging_analyze.md
@@ -1,10 +1,14 @@
-## Analyzing crashes
+<!-- ## Analyzing crashes -->
+## 分析崩溃
 
+<!-- 
 Fuchsia starts a program at boot called `crashanalyzer` that reports program
 crashes and prints a backtrace of the crashing thread to the system log. While
 you can explore these directly by reviewing the logs at runtime, the backtrace
 content is encoded using the stack memory address references rather than
 pointing to the corresponding lines in the program source files.
+ -->
+Fuchsia 在启动时启动一个名为 `crashanalyzer` 的程序，该程序报告程序崩溃并将崩溃线程的回溯打印到系统日志中。虽然您可以通过在运行时查看日志来直接浏览这些内容，但回溯内容是使用堆栈内存地址引用编码的，而不是指向程序源文件中的相应行。
 
 
 ```none {:.devsite-disable-click-to-copy}
@@ -38,6 +42,7 @@ pointing to the corresponding lines in the program source files.
 [klog][I] bt#05: end
 ```
 
+<!-- 
 This is because the **debug symbols** are stripped out of the core binaries
 by default at build time. To properly analyze the crash log, you need to
 reapply those symbols to the backtrace to see the call stack in terms of source
@@ -45,12 +50,17 @@ code line numbers. When you call the `ffx log` command, the developer tools
 process the raw log through an additional binary called `symbolizer` that
 reapplies the symbols from your local build configuration to any backtraces in
 the log.
+ -->
+这是因为 **调试符号** 在构建时默认从二进制文件中删除。要正确分析崩溃日志，您需要将这些符号重新应用到回溯，以根据源代码行号查看调用堆栈。当您调用 `ffx log` 命令时，开发人员工具会通过一个名为 `symbolizer` 的附加二进制文件处理原始日志，该二进制文件将本地构建配置中的符号重新应用到日志中的任何回溯。
 
 ```posix-terminal
 ffx log
 ```
 
+<!-- 
 The output you see includes the symbols reapplied to the backtrace:
+ -->
+您看到的输出包括重新应用于回溯的符号：
 
 ```none {:.devsite-disable-click-to-copy}
 [klog][I] devmgr: crash_analyzer_listener: analyzing exception type 0x108
@@ -64,48 +74,77 @@ end of symbolized stack
 ```
 
 <aside class="key-point">
+<!-- 
 If you have a manually captured backtrace, you can run the same process by
 passing the content through the <code>ffx debug symbolize</code> command.
+ -->
+如果您有手动捕获的回溯，则可以通过 <code>ffx debug symbolize</code> 命令传递内容来运行相同的过程。
 </aside>
 
+<!-- 
 With a properly symbolized backtrace, you can directly discover the site of a
 crash in your source code.
+ -->
+通过正确符号化的回溯，您可以直接在源代码中发现崩溃的位置。
+<!-- ### Step-through debugging -->
+### 逐步调试
 
-### Step-through debugging
-
+<!-- 
 Just knowing where a program crashed may not be enough information to fully
 diagnose the issue. Sometimes it's necessary to walk through the code
 step-by-step and even inspect the state of variables in memory. To support this,
 Fuchsia has a debugger for core code called `zxdb`.
+ -->
+仅仅知道程序崩溃的位置可能不足以完全诊断问题。 有时需要一步一步地遍历代码，甚至检查内存中变量的状态。 为了支持这一点，Fuchsia 有一个名为 `zxdb` 的核心代码调试器。
 
+<!-- 
 The `zxdb` tool is a client that connects to a running `debug_agent` component
 on the target device. You can use the `zxdb` commands to configure the
 `debug_agent` to attach to specific processes and set breakpoints. Once a debug
 session is attached to a running process, `zxdb` allows you to step through the
 code and inspect the stack frames.
+ -->
+`zxdb` 工具是一个客户端，它连接到目标设备上正在运行的 `debug_agent` 组件。您可以使用 `zxdb` 命令进行配置，然后使用 `debug_agent` 附加到特定进程并设置断点。一旦调试会话附加到正在运行的进程，`zxdb` 允许您单步执行代码并检查堆栈帧。
 
+<!-- 
 ![Diagram showing how the Fuchsia debugger (zxdb) interacts with the
 debug_agent service running on a Fuchsia device to perform interactive
 debugging of a process.](/get-started/images/components/zxdb.png){: width="591"}
+ -->
+![图表显示了 Fuchsia 调试器 (zxdb) 如何与运行在 Fuchsia 设备上的 debug_agent 服务交互，以执行进程的交互调试。](/get-started/images/components/zxdb.png){: width="591"}
 
-Setting up the debug session requires the following high-level steps:
-
+<!-- Setting up the debug session requires the following high-level steps: -->
+设置调试会话需要以下高级步骤：
+<!-- 
 1.  Run the `debug_agent` component on the target device.
 1.  Run the `zxdb` client and connect to the target device.
 1.  Set the location for `zxdb` to find debug symbols.
+ -->
+1.  在目标设备上运行 `debug_agent` 组件。
+1.  运行 `zxdb` 客户端并连接到目标设备。
+1.  设置 `zxdb` 的位置以查找调试符号。
 
+<!-- 
 The simplest method to start a debug session is to use the `ffx debug connect`
 command, which does all of these in the context of your local Fuchsia build.
 However, these steps can also be performed manually if you need to configure
 them separately.
+ -->
+启动调试会话的最简单方法是使用 `ffx debug connect` 命令，该命令在本地 Fuchsia 构建的上下文中执行所有这些操作。然而，如果您需要单独配置这些步骤，也可以手动执行。
 
+<!-- 
 Once the debug session is active, you are taken to a `[zxdb]` prompt to issue
 debugger commands. You can use `zxdb` to configure the `debug_agent` to attach
 to a process using a name filter and set pending breakpoints even if no
 matching process is currently running.
+ -->
+一旦调试会话处于活动状态，您将被带到 `[zxdb]` 提示符以发出调试器命令。您可以使用 `zxdb` 来配置 `debug_agent` 以使用名称过滤器附加到进程，并设置挂起断点，即使当前没有匹配到正在运行的进程。
 
+<!-- 
 The following example sets a pending breakpoint on main to stop at the
 beginning of execution, and waits for a process called "hello-world" to start:
+ -->
+以下示例在 main 上设置一个挂起的断点以在执行开始时停止，并等待名为“hello-world”的进程启动：
 
 ```none {:.devsite-disable-click-to-copy}
 [zxdb] attach hello-world
@@ -117,53 +156,84 @@ Pending: No matches for location, it will be pending library loads.
 ```
 
 <aside class="caution">
-  <b>Launching components with zxdb</b>
+  <!-- <b>Launching components with zxdb</b> -->
+  <b>使用 zxdb 启动组件</b>
+  <!-- 
   <p>The Fuchsia debugger supports two main methods of debugging a process:
   <code>run</code> and <code>attach</code>. Avoid using <code>run</code> to
   start and debug components.</p>
+   -->
+  <p>Fuchsia 调试器支持两种主要的进程调试方法：<code>run</code> 和 <code>attach</code>。避免使用 <code>run</code> 来启动和调试组件。</p>
 
+  <!-- 
   <p>When the debugger launches a component, the component will have the same
   capabilities as the <code>debug_agent</code>. The only way to get the correct
   environment is to launch your component in the way it expects and attach the
   debugger to it.</p>
+   -->
+  <p>当调试器启动一个组件时，该组件将具有与 <code>debug_agent</code> 相同的功能。获得正确环境的唯一方法是以预期的方式启动组件，并将调试器附加到组件上。</p>
 </aside>
 
+<!-- 
 Once the debugger is attached to a process, you can use `zxdb` commands to
 control and inspect the state of the process. Here is a short collection of
 common commands:
+ -->
+将调试器附加到进程后，您可以使用 `zxdb` 命令来控制和检查进程的状态。以下是常用命令的简短集合：
 
-Note: For complete details and reference on `zxdb` commands, see
-[The Fuchsia debugger](/development/debugger).
+<!-- Note: For complete details and reference on `zxdb` commands, see
+[The Fuchsia debugger](/development/debugger). -->
+注意：关于 `zxdb` 命令的完整详细信息和参考，请查看 [Fuchsia 调试器](/development/debugger)。
 
 <table>
   <tr>
    <td><code>step</code>
    </td>
+   <!-- 
    <td>Step over the next line of code in the thread
+   </td>
+    -->
+   <td>步过线程中的下一行代码
    </td>
   </tr>
   <tr>
    <td><code>next</code>
    </td>
+   <!-- 
    <td>Step into the next line of code in the thread
+   </td>
+    -->
+   <td>步入线程中的下一行代码
    </td>
   </tr>
   <tr>
    <td><code>continue</code>
    </td>
+   <!-- 
    <td>Continue execution until the next breakpoint, exception, or exit
+   </td>
+    -->
+   <td>继续执行直到下一个断点、异常或退出
    </td>
   </tr>
   <tr>
    <td><code>frame</code>
    </td>
+   <!-- 
    <td>List or select from the current stack frames
+   </td>
+    -->
+   <td>列出或从当前堆栈帧中选择
    </td>
   </tr>
   <tr>
    <td><code>print</code>
    </td>
+   <!-- 
    <td>Evaluate an expression and print the result
+   </td>
+    -->
+   <td>求表达式的值并打印结果
    </td>
   </tr>
 </table>