summaryrefslogtreecommitdiff
path: root/src/third_party/wiredtiger/tools/antithesis/README
diff options
context:
space:
mode:
Diffstat (limited to 'src/third_party/wiredtiger/tools/antithesis/README')
-rw-r--r--src/third_party/wiredtiger/tools/antithesis/README8
1 files changed, 8 insertions, 0 deletions
diff --git a/src/third_party/wiredtiger/tools/antithesis/README b/src/third_party/wiredtiger/tools/antithesis/README
index 10b3d8a43fb..57504bfc6a2 100644
--- a/src/third_party/wiredtiger/tools/antithesis/README
+++ b/src/third_party/wiredtiger/tools/antithesis/README
@@ -24,3 +24,11 @@ Alternatively, you can create an evergreen patch build from this branch and trig
which will build the containers and upload to Antithesis directly.
We are including libstarvoid which helps with Antithesis integration.
+
+Using the debugger
+To launch a debugger for a core that has been generated by a container, you can do the following:
+
+1. Spawn a host from the task that generated the container.
+2. Untar the artifacts so you have the same binaries.
+3. Change directory to the tools/antithesis directory (this directory).
+4. Execute "./launch_gdb.sh <core>" where core is the core file you wish to debug. This will launch gdb in the container.