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

Passing through the line number/ position in the source that caused an error #54

Open
nielstron opened this issue Feb 15, 2023 · 0 comments
Labels
bb: minor Minor issue according to bug bounty categorization bug bounty This issue is prized out as part of the Bug Bounty Program enhancement New feature or request

Comments

@nielstron
Copy link
Contributor

nielstron commented Feb 15, 2023

Is your feature request related to a problem? Please describe.
Debugging contracts on-chain is always difficult. In particular one might be interested in the precise location of the error in the original source (similar to a traceback in python)

Describe the solution you'd like
A traceback is infeasible, but error messages could be tagged with the line in the original source code that caused the error at compilation time. What needs to be worked out is to how to display the line number nicely, so that it might look similar to a python traceback.

This likely requires passing through the line number of the invocation of some higher level functions at compile time.

Describe alternatives you've considered
None

Additional context
None

Bug bounty: 200 ADA

@nielstron nielstron added the enhancement New feature or request label Feb 15, 2023
@nielstron nielstron added bug bounty This issue is prized out as part of the Bug Bounty Program bb: minor Minor issue according to bug bounty categorization labels Aug 21, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bb: minor Minor issue according to bug bounty categorization bug bounty This issue is prized out as part of the Bug Bounty Program enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant