From 09b273c0b8c2c7f6cf4c3e9511e39a17bc6e6985 Mon Sep 17 00:00:00 2001 From: Daniel Matichuk Date: Thu, 15 Aug 2024 11:31:45 -0700 Subject: [PATCH] Update docs/user-manual/binary-ninja-ui.tex Co-authored-by: Ben Davis --- docs/user-manual/binary-ninja-ui.tex | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/user-manual/binary-ninja-ui.tex b/docs/user-manual/binary-ninja-ui.tex index 144e015a..e83c1206 100644 --- a/docs/user-manual/binary-ninja-ui.tex +++ b/docs/user-manual/binary-ninja-ui.tex @@ -125,7 +125,7 @@ \subsection{Trace Constraints} \label{fig:equiv-cond-full} \end{figure} -When "Constrain Trace" is clicked, the "Trace Constraint" window (see Figure~\ref{fig:trace-constr-empty}) appears. The +When ``Constrain Trace'' is clicked, the ``Trace Constraint'' window (see Figure~\ref{fig:trace-constr-empty}) appears. The "Variable" dropdown is populated with the memory reads from both the original and patched programs. Notably each read is prefixed with the instruction address that the read occurred at, indicating that the constraint applies to the content of memory at that specific program point. The user then selects a relation and enters an integer value to compare the