Skip to content

Conversation

@Steve0Greatness
Copy link

@Steve0Greatness Steve0Greatness commented Aug 7, 2025

Unfinished ATM, just making a draft PR so feedback is easier.

This PR adds better tracebacking functionality to the debugging extension, with it even (hypothetically) working across targets (although I haven't tested it, yet).

This also adds a reference to the parent thread for the HATS_STARTED event, allowing for this PR to even be possible.

TODO

  • Add tracebacking for procedures (custom blocks). I have to figure out how to get the VM to update the traceback when the thread enters or exits a procedure.
  • The same might also be nice to have for branches, as well.
  • Finish the _renderTraceback method under the extension itself. I'd like to have it add links to the specific target and script that it references, since I think that'd be useful.

Start of implementing a traceback using the debugging extension
So it adds the parent thread to match with the block-utility one.
This could allow for more stuff to take advantage of the system, as
well, it makes it a bit easier to manage since it won't require
everything to have events attached.
It's under a different event, now, which should be called more often.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant