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
[RFC] Show the source line number of the Meson build definition when a Meson exception is thrown and printed #9365
Comments
This is not a Meson exception. Meson exceptions do print line numbers. This is a meson bug, throwing a python traceback and must be fixed. |
Duplicate of #9350 |
Ah, indeed. Thanks! |
For the record, since 3c039f4 we report a better error on python exceptions too. We still print the full traceback, but we follow up on that with something like: meson.build:1234:0: ERROR: Unhandled python exception
This is a Meson bug and should be reported! This also means that
this will be clearly contradicted by Meson. Meson knows that anything which produces a traceback is automatically a bug, if for no other reason than that all errors should be caught and communicated clearly with regard to why meson considers it problematic... so when Meson encounters an unrecognizable traceback, it tells you that you should report it as a bug to us. The meson.build line number context is provided too, to help narrow down what meson.build content triggered an internal error. |
If a Meson exception is thrown then it's probably the fault of the Meson build definition (meson.build) of the project. The user is presented with a call stack but doesn't know which statement in
meson.build
caused thatToday I tried building GIMP using Meson from the main branch. I get a Meson exception but I don't quite know where to look at in the Meson build definitions:
It'd be very useful to know the meson.build and line number / op that is being parsed or interpreted.
The text was updated successfully, but these errors were encountered: