Skip to content

Commit 3e58183

Browse files
committed
Fixes
1 parent fa7a618 commit 3e58183

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

docs/platforms/godot/configuration/stack-traces.mdx

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -3,9 +3,9 @@ title: Readable Stack Traces
33
description: "Learn how to get readable stack traces in Sentry with Sentry SDK for Godot Engine."
44
---
55

6-
Debug information files allow Sentry to extract stack traces and provide additional information about crash reports. In order to get readable stack traces in Sentry when your game crashes, you need to export your project using an export template that includes debug symbols. For the official builds, Godot Engine only provides templates without debug information. This guide covers how to create such templates and use them to export your project with full debug information available in Sentry.
6+
Debug information files allow Sentry to extract stack traces and provide additional information about crash reports. In order to get readable stack traces in Sentry when your game crashes, you need to export your project using an export template that contains debug information. For the official builds, Godot Engine only provides templates without debug symbols. This guide covers how to create such templates and use them to export your project with full debug information available in Sentry.
77

8-
To get debug information, we need to compile export templates with debug symbols included. You'll need **SCons** build tool, Python, and a C++ compiler for your target platform installed.
8+
To get debug information, we need to compile export templates with debug symbols produced. You'll need **SCons** build tool, Python, and a C++ compiler for your target platform installed.
99

1010
<Alert>
1111

@@ -74,7 +74,7 @@ If you need to `Export with Debug`, you can compile a debug template using the `
7474

7575
## Uploading Debug Symbols
7676

77-
In order to see readable stack traces in Sentry, you also need to upload your debug symbols. The easiest way to do it is by using Sentry CLI tools. These tools allow you to upload the necessary debug information, making the stack traces more readable and easier to debug.
77+
In order to see readable stack traces in Sentry, you also need to upload your debug symbols. The easiest way to do it is by using Sentry CLI tools. These tools allow you to upload the necessary debug information, making the stack traces useful for debugging.
7878

7979
<Expandable title="Installing Sentry CLI">
8080

0 commit comments

Comments
 (0)