Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Make sure uncaught exception is in last debug frame #652

Open
pdawyndt opened this issue Mar 8, 2024 · 1 comment
Open

Make sure uncaught exception is in last debug frame #652

pdawyndt opened this issue Mar 8, 2024 · 1 comment

Comments

@pdawyndt
Copy link
Contributor

pdawyndt commented Mar 8, 2024

If an uncaught runtime exception is raised while running the Python code, the last debug frame should show that runtime error:

image

Now, the runtime error is shown in the penultimate debug frame, whereas nothing can be observed in the last debug frame

image

Source: https://dodona.be/nl/courses/3355/series/36011/activities/2055708402/

This seems behaviour that is inherited from the original Python Tutor, which even behaves worse:

Runtime error is reported in the penultimate debug frame

image

but this is followed by another debug frame

image

which is followed by yet another debug frame where the debug frame appears again

image

(probably reflects how runtime exception percolates through call stack)

@pdawyndt
Copy link
Contributor Author

pdawyndt commented Mar 8, 2024

Version of Python Tutor in Papyros actually seems to behave exactly as the original Python Tutor (but instead of marking the extra debug frame as "Done running (?? steps)", it is not available in the debug trace.

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

No branches or pull requests

1 participant