ZDoom

StateProvider.A_FirePistol at gzdoom.pk3:zscript/doom/weaponpistol.txt, line 78
PSprite.Tick at gzdoom.pk3:zscript/shared/player.txt, line 1345
PlayerPawn.TickPSprites at gzdoom.pk3:zscript/shared/player.txt, line 399
PlayerPawn.PlayerThink at gzdoom.pk3:zscript/shared/player.txt, line 1194

Using linked list of [b]VMFrame[/b] objects from [b]GlobalVMStack[/b] I was able to collect the following:[code]StateProvider.A_FirePistol at gzdoom.pk3:zscript/doom/weaponpistol.txt, line 78
PSprite.Tick at gzdoom.pk3:zscript/shared/player.txt, line 1345
PlayerPawn.TickPSprites at gzdoom.pk3:zscript/shared/player.txt, line 399
PlayerPawn.PlayerThink at gzdoom.pk3:zscript/shared/player.txt, line 1194[/code]
This is the best output we can offer without altering the VM. For example, call stack traversal stops on the first native function.

Cannot be done. To print a stack trace you have to unwind the stack which automatically makes it fatal. The stack we are talking here is not some VM construct, but the actual CPU stack.

When the game is aborted from ZScript (divide by zero, ThrowAbortException, etc), the current ZScript call stack is (sometimes?) shown on the console. This aids debugging, but only if the error is fatal. It would be helpful to be able to emit a stack trace for non-fatal errors too.