diff --git a/gdb-port/parser.py b/gdb-port/parser.py
index fdec982f708057c4c858339fef25e2e2e13f9818..6720d5fea05c245a387bf7f5d8780f605b813fd4 100644
--- a/gdb-port/parser.py
+++ b/gdb-port/parser.py
@@ -296,14 +296,19 @@ class ParserStack:
 	# Represented by a '(' for push, and ')' pop, a typical list of stack events might look like:
 	# (()(())((()((((()(((((
 
+	# This can be broken up to the following:
+	#	a string of pushes at the start of the list + a push/pop pair enclosing other push/pop pairs or string of pushes + another, optional, string of pushes at the end of the list
+
+	# The typical string above can be broken up like this:
+	# ( | ()(())((()((((() | (((((
+
 	# Key observations
-	# There is either a run of "push" events at the top of the stack, or there is a "pop" event
+	# There is either a run of "push" events at the end of the list, or there is a "pop" event
 	# While a "pop" will always have a corresponding "push" event, there may be runs of "push" events without a "pop" between the push/pop pair
 	# In terms of parentheses, assuming an intact execution flow, there will never be a stray right parenthesis, but there may be an arbitrary amount of open parentheses
 	# "pop" events trigger committing their allocations to the memory stats
-	# For UX purposes, the left parens should also be committed as soon as possible, without double-counting the allocations made before calling h_do_parse() again, or returning 
+	# For UX purposes, the left parens should also be committed as soon as possible, without double-counting the allocations made before calling h_do_parse() again, or returning
 
-	# TODO: perhaps a "pop" should act as a checkpoint, and commit every allocation up to that point
 
 	def calculate_and_clear_pushes_at_end(self):
 		stats = self.calculate_pushes_at_end()