| Summary: | KDevelop segfaults whilst editing code | ||
|---|---|---|---|
| Product: | [Frameworks and Libraries] frameworks-ktexteditor | Reporter: | ian.c.whiting |
| Component: | general | Assignee: | KWrite Developers <kwrite-bugs-null> |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | crash | CC: | mail, waqar.17a |
| Priority: | NOR | Keywords: | drkonqi |
| Version First Reported In: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | openSUSE | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
|
Description
ian.c.whiting
2022-09-13 11:12:19 UTC
Moving to KTextEditor, this crash backtrace is from the JS engine executing the autoindenter script after keypress. which language? and if possible can you share the code or simplified/modified version of the code where it crashes, otherwise its unlikely it will get fixed. The language is C++. Unfortunately I cannot share the code. I am happy to try to trace the issue myself if you can provide pointers to where I should start looking. You don't have to share the exact code, just the piece of code where it crashes and then create some dummy code similar to it which can repro the problem. If you want to try yourself, cstyle.js is the file you want to look at in KTextEditor repo https://invent.kde.org/frameworks/ktexteditor/ you can just copy that file locally and try to debug that or just work directly in the repo, see: https://docs.kde.org/trunk5/en/kate/katepart/dev-scripting.html Without sample code with which the crash can be reproduced, this can't be fixed Marking as NEEDSINFO, it will auto close in a few days Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! |