-
-
Notifications
You must be signed in to change notification settings - Fork 1.4k
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
Showing
1 changed file
with
26 additions
and
19 deletions.
There are no files selected for viewing
45 changes: 26 additions & 19 deletions
45
src/platforms/common/data-management/debug-files/source-context.mdx
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,19 +1,26 @@ | ||
--- | ||
title: Source Context | ||
sidebar_order: 5 | ||
description: "Learn about setting up source bundles to show source code in stack traces on the Issue Details page." | ||
--- | ||
|
||
If Sentry has access to application source code, it can show snippets of code | ||
around the location of stack frames. Certain SDKs can resolve this source | ||
context automatically, such as the Python SDK, because they have access to | ||
unobfuscated source code at runtime. | ||
|
||
To get source context for native applications, source code needs to be uploaded | ||
alongside the debug information files. The recommended way to do this is by | ||
using `sentry-cli`. See [Creating Source Bundles](/product/cli/dif/#creating-source-bundles) for more information. | ||
|
||
Source bundles show up as regular debug files on the _Debug Files_ settings | ||
page. They are designated as "source bundle" and feature a `sources` tag. To | ||
match them with crash reports, they carry the same debug file as the respective | ||
debug information file they have been created from. | ||
--- | ||
title: Source Context | ||
sidebar_order: 5 | ||
description: "Learn about setting up source bundles to show source code in stack traces on the Issue Details page." | ||
--- | ||
|
||
If Sentry has access to application source code, it can show snippets of code | ||
around the location of stack frames. Certain SDKs can resolve this source | ||
context automatically, such as the Python SDK, because they have access to | ||
unobfuscated source code at runtime. | ||
|
||
To get source context for native applications, source code needs to be uploaded | ||
alongside the debug information files. The recommended way to do this is by | ||
using `sentry-cli`. See [Creating Source Bundles](/product/cli/dif/#creating-source-bundles) for more information. | ||
|
||
Source bundles show up as regular debug files on the _Debug Files_ settings | ||
page. They are designated as "source bundle" and feature a `sources` tag. To | ||
match them with crash reports, they carry the same debug file as the respective | ||
debug information file they have been created from. | ||
|
||
<PlatformSection supported={["dotnet"]}> | ||
|
||
Alternatively, you can build your project with `<EmbedAllSources>true</EmbedAllSources>` project property to produce | ||
a Portable PDB with embedded source code. You can upload these PDB files using `sentry-cli` as usual. | ||
|
||
</PlatformSection> |