code/__HELPERS/stack_trace.dm

/proc/_stack_trace	gives us the stack trace from CRASH() without ending the current proc. Do not call directly, use the stack_trace macro instead.
/proc/dump_stack	Returns an ordered list of all our parent procs, highest to deepest Note: This will frequently cause erorrs and have seemingly infinitely repeating procs on the current good byond version It'll be fixed when we can update to latest for dev but you likely can't do that right now (since debugging hasn't been fixed yet) BIGGER, MORE IMPORTANT NOTE: Should not be used on master maybe ever, introspection like this is mostly useful for debugging if you have another use I suspect you are just creating god's strongest footgun and should rethink things

/proc/_stack_trace

gives us the stack trace from CRASH() without ending the current proc. Do not call directly, use the stack_trace macro instead.

/proc/dump_stack

Returns an ordered list of all our parent procs, highest to deepest Note: This will frequently cause erorrs and have seemingly infinitely repeating procs on the current good byond version It'll be fixed when we can update to latest for dev but you likely can't do that right now (since debugging hasn't been fixed yet) BIGGER, MORE IMPORTANT NOTE: Should not be used on master maybe ever, introspection like this is mostly useful for debugging if you have another use I suspect you are just creating god's strongest footgun and should rethink things