Skip to content

Commit 7b212d0

Browse files
authored
Update links to crashpad releases (#3168)
1 parent 9cc6cc5 commit 7b212d0

File tree

3 files changed

+3
-3
lines changed

3 files changed

+3
-3
lines changed

docs/error-reporting/language-integrations/mixed.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -47,7 +47,7 @@ Configuring your application environments to report Crashes and Exceptions is th
4747

4848
1. Ensure that you have created a Backtrace instance and obtained a submission token for your project. Both C# and C++ crash reports should be sent to the same project.
4949
2. Review the [Readme](https://github.com/backtrace-labs/backtrace-csharp/blob/master/README.md) for the Backtrace C# reporting library. Follow the instructions to download and configure the library. Also, review the options for offline storage and submission of crash reports. Integrate the Backtrace C# library into your C# applications.
50-
3. Read the [Crashpad Integration Guide](/error-reporting/platform-integrations/crashpad/) and follow the instructions to use Backtrace's Crashpad binaries. You can [download the binaries](http://get.backtrace.io/crashpad/builds/) and view the source code on the [Backtrace branch on Github](https://github.com/backtrace-labs/crashpad/tree/backtrace). These binaries include additional features not available in the community-maintained (master) branch. Specifically, you can attach files to C++ crash reports, and generate a minidump even when a crash doesn't occur. This is useful for mixed call stacks because most C++ functions called from C# include exception handling code to allow the system to recover. However, engineers still need a minidump file to understand the call stack and investigate the root cause. Refer to the "Send reports using EXCEPTION_POINTERS in Windows" section in the [Readme](https://github.com/backtrace-labs/crashpad/blob/backtrace/README.md#send-reports-using-exception_pointers-in-windows) for more details.
50+
3. Read the [Crashpad Integration Guide](/error-reporting/platform-integrations/crashpad/) and follow the instructions to use Backtrace's Crashpad binaries. You can [download the binaries](https://github.com/backtrace-labs/crashpad/releases/) and view the source code on the [Backtrace branch on Github](https://github.com/backtrace-labs/crashpad/tree/backtrace). These binaries include additional features not available in the community-maintained (master) branch. Specifically, you can attach files to C++ crash reports, and generate a minidump even when a crash doesn't occur. This is useful for mixed call stacks because most C++ functions called from C# include exception handling code to allow the system to recover. However, engineers still need a minidump file to understand the call stack and investigate the root cause. Refer to the "Send reports using EXCEPTION_POINTERS in Windows" section in the [Readme](https://github.com/backtrace-labs/crashpad/blob/backtrace/README.md#send-reports-using-exception_pointers-in-windows) for more details.
5151

5252
## Sample Code And Custom Attributes to Include in Crash And Exception Reports
5353

docs/error-reporting/platform-integrations/crashpad.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -118,7 +118,7 @@ It is always possible to build Crashpad from the source. To do this, see the [Ba
118118

119119
#### Download Built Libraries
120120

121-
Backtrace provides builds of Crashpad. We recommend using the stable version. The latest stable releases of Backtrace's Crashpad fork are available at [http://get.backtrace.io/crashpad/builds/](http://get.backtrace.io/crashpad/builds/), and the Backtrace fork nightly builds can be found [on GitHub](https://github.com/backtrace-labs/crashpad/actions).
121+
Backtrace provides builds of Crashpad. We recommend using the stable version. The latest stable releases of Backtrace's Crashpad fork are available at [https://github.com/backtrace-labs/crashpad/releases/](https://github.com/backtrace-labs/crashpad/releases/), and the Backtrace fork nightly builds can be found [on GitHub](https://github.com/backtrace-labs/crashpad/actions).
122122

123123
### Integrate Crashpad
124124

docs/error-reporting/platform-integrations/file-attachments.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -79,7 +79,7 @@ See the [Breakpad Integration Guide](/error-reporting/platform-integrations/brea
7979

8080
## Crashpad
8181

82-
Crashpad is another open source library initially developed by Google as a successor to the Breakpad library. Backtrace has built and released a set of binaries of Crashpad for Windows (64 and 32 bit) that include an ability to upload file attachments. Check out http://get.backtrace.io/crashpad/builds/ to download the binaries for your OS.
82+
Crashpad is another open source library initially developed by Google as a successor to the Breakpad library. Backtrace has built and released a set of binaries of Crashpad for Windows (64 and 32 bit) that include an ability to upload file attachments. Check out https://github.com/backtrace-labs/crashpad/releases/ to download the binaries for your OS.
8383

8484
To provide you with the ability to upload files, we have implemented a new handler to make file attachments just as simple as setting up any other piece of metadata to come alongside the crash.
8585

0 commit comments

Comments
 (0)