https://bugs.kde.org/show_bug.cgi?id=403098
--- Comment #2 from Francis Herne <m...@flherne.uk> ---
I don't think it is, there's no annotated assignment in the call stack...
Looks similar, though.
To the reporter:
Thanks for the report.
The crash is in the Python parser, probably triggered by some specific
combination of syntax.
If you run `export QT_LOGGING_RULES="kdevelop.plugins.python=true"` before
starting KDevelop, it will print (among other things) lines of the format
`kdevelop.plugins.python: ====> PARSING ====> parsing file
QUrl("file:///home/flh/foo.py") ; has priority -10000`
This should identify the file being parsed at the time of the crash.
The call stack in your crash report should help find the specific part
responsible; it involved:
- An attribute access
- Inside a list comprehension
- As part of a function call (either as an argument, or the thing being
called)
- At the top level of a function body.
If you can produce a minimal example (perhaps with variable names etc.
anonymized) that would help identify and fix the problem.
Note: I have tried to reproduce the issue just by looking at the call stack,
but without success so far.
--
You are receiving this mail because:
You are watching all bug changes.
