Skip to content
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.

Commit 2273afb

Browse files
authoredJun 7, 2024
Fix dbghelp comment (#630)
1 parent 9b7c378 commit 2273afb

File tree

2 files changed

+4
-4
lines changed

2 files changed

+4
-4
lines changed
 

‎src/backtrace/dbghelp32.rs‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
1-
//! Backtrace strategy for MSVC platforms.
1+
//! Backtrace strategy for Windows platforms.
22
//!
3-
//! This module contains the ability to generate a backtrace on MSVC using one
3+
//! This module contains the ability to generate a backtrace on Windows using one
44
//! of two possible methods. The `StackWalkEx` function is primarily used if
55
//! possible, but not all systems have that. Failing that the `StackWalk64`
66
//! function is used instead. Note that `StackWalkEx` is favored because it

‎src/backtrace/dbghelp64.rs‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
1-
//! Backtrace strategy for MSVC `x86_64` and `aarch64` platforms.
1+
//! Backtrace strategy for Windows `x86_64` and `aarch64` platforms.
22
//!
3-
//! This module contains the ability to capture a backtrace on MSVC using
3+
//! This module contains the ability to capture a backtrace on Windows using
44
//! `RtlVirtualUnwind` to walk the stack one frame at a time. This function is much faster than using
55
//! `dbghelp!StackWalk*` because it does not load debug info to report inlined frames.
66
//! We still report inlined frames during symbolization by consulting the appropriate

0 commit comments

Comments
 (0)
Please sign in to comment.