Skip to content

Commit 67706d2

Browse files
author
Hubert Tong
committed
is_debugger_present: Clarify intent to avoid false positives
The wording implies a preference to return `true` in case it is unknown whether a debugger is present. Add a critical "only" to fix that.
1 parent a5c7585 commit 67706d2

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

source/diagnostics.tex

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -2493,13 +2493,13 @@
24932493
\impldef{default semantics of \tcode{is_debugger_present}}.
24942494

24952495
\begin{note}
2496-
It is intended that, when tracing the execution of a program with a debugger, an
2497-
implementation returns \tcode{true} with the use of an immediate query, as
2498-
needed, to determine if the program is being traced by a debugger. On Windows or
2496+
It is intended that, using an immediate (uncached) query to determine if the
2497+
program is being traced by a debugger, an implementation returns \tcode{true}
2498+
only when tracing the execution of the program with a debugger. On Windows or
24992499
equivalent systems, this can be achieved by calling the
25002500
\tcode{::IsDebuggerPresent()} Win32 function. For systems compatible with
25012501
ISO/IEC 23360:2021, this can be achieved by checking for a tracing process, with
2502-
best effort determination that such a tracing process is a debugger.
2502+
a best-effort determination that such a tracing process is a debugger.
25032503
\end{note}
25042504

25052505
\end{itemdescr}

0 commit comments

Comments
 (0)