picotron error explorer 0.0.6 - interactive stack trace on error

snowkittykira • 2024-04-26*2024-04-26 17:36* •

hi, i wrote an interactive error screen for picotron! on error, it lets you explore the stack, local variables, and shows the source location where the error occurred. use arrows to go up and down the stack, the mouse wheel to scroll, and click on table variables to expand them. you can also press space or x to toggle small-font mode.

error_explorer_example

by snowkittykira

Cart #error_explorer_example-0 | 2024-04-26 | Embed ▽ | License: CC4-BY-NC-SA

download: https://github.com/snowkittykira/picotron-error-explorer

to use it, download error_explorer.lua and include it after defining your _init, _update and _draw functions.

it replaces these functions which wrappers that call them in a coroutine, so that when errors happen the coroutine can be inspected. on error, it does its best to reset the graphics state, but there might still be cases where this fails so let me know if you run into any issues!

it relies on the following functions from lua's debug library, so i hope they will continue to be available:

debug.traceback
debug.getinfo
debug.getlocal
debug.getupvalue

(note: please use the github version and not the one in the example cart, as it'll be more up to date)

MaddoScientisto • 2024-04-27*2024-04-27 13:24*

THANK YOU!!
I was becoming insane trying to figure out what went wrong sometimes, considering I haven't found a convenient log function

Can I also use it to trigger a kind of debug error myself to inspect a specific location?

snowkittykira • 2024-04-27*2024-04-27 16:15*

thanks~!

you should be able to call error("message") to trigger it wherever you want. also, if you run picotron from a command line, you can use printh("message") to log to the terminal (this is built in to picotron). error explorer dumps the error message / backtrace to printh as well in case that's helpful!