rather than using common practice or convention as an implicit
understanding between producer and consumer. For example, where
other debugging formats assume that a debugger knows how to
+\bb
+virtually
+\eb
unwind the stack, moving from one stack frame to the next using
implicit knowledge about the architecture or operating system,
DWARF makes this explicit in the Call Frame Information description.