From 47e4be153689b099d3005c4e7e33e0c6ffc53f03 Mon Sep 17 00:00:00 2001
From: Frederick Muriuki Muriithi
Date: Mon, 22 May 2023 08:55:47 +0300
Subject: Add missing example.

---
 topics/using-pdb-to-troubleshoot.gmi | 6 ++++++
 1 file changed, 6 insertions(+)

(limited to 'topics')

diff --git a/topics/using-pdb-to-troubleshoot.gmi b/topics/using-pdb-to-troubleshoot.gmi
index 4cfe616..294486f 100644
--- a/topics/using-pdb-to-troubleshoot.gmi
+++ b/topics/using-pdb-to-troubleshoot.gmi
@@ -116,6 +116,12 @@ the process, leading to the error above. Generally speaking, you **SHOULD NOT**
 be running the debugger in production anyway, and therefore you should not need
 to deal with the gunicorn issues.
 
+That said, you can start the Flask application under pdb with something like:
+
+```
+python3 -m pdb flask run [OPTIONAL-ARGUMENTS-TO-FLASK]
+```
+
 
 ## Useful Tutorials
 
-- 
cgit v1.2.3