Add --trace-{match,execute} options

These options can be used to understand which dependency chain causes matching
or execution of a particular target.

1 files changed, 23 insertions, 9 deletions

diff --git a/libbuild2/b.cli b/libbuild2/b.cli
index 3ae6e0b..dc5198e 100644
--- a/libbuild2/b.cli
+++ b/libbuild2/b.cli
@@ -537,15 +537,6 @@ namespace build2
       "Display build statistics."
     }
 
-    std::set<string> --dump
-    {
-      "<phase>",
-      "Dump the build system state after the specified phase. Valid <phase>
-       values are \cb{load} (after loading \cb{buildfiles}) and \cb{match}
-       (after matching rules to targets). Repeat this option to dump the
-       state after multiple phases."
-    }
-
     bool --progress
     {
       "Display build progress. If printing to a terminal the progress is
@@ -742,6 +733,29 @@ namespace build2
        \cb{--mtime-check} for details."
     }
 
+    std::set<string> --dump
+    {
+      "<phase>",
+      "Dump the build system state after the specified phase. Valid <phase>
+       values are \cb{load} (after loading \cb{buildfiles}) and \cb{match}
+       (after matching rules to targets). Repeat this option to dump the
+       state after multiple phases."
+    }
+
+    std::vector<name> --trace-match
+    {
+      "<target>",
+      "Trace rule matching for the specified target. This is primarily useful
+       during troubleshooting. Repeat this option to trace multiple targets."
+    }
+
+    std::vector<name> --trace-execute
+    {
+      "<target>",
+      "Trace rule execution for the specified target. This is primarily useful
+       during troubleshooting. Repeat this option to trace multiple targets."
+    }
+
     bool --no-column
     {
       "Don't print column numbers in diagnostics."