Bug 424703 - KDevelop keeps crashing while parsing a (C++) file
Summary: KDevelop keeps crashing while parsing a (C++) file
Status: RESOLVED WORKSFORME
Alias: None
Product: kdevelop
Classification: Applications
Component: general (show other bugs)
Version: 5.5.0
Platform: Ubuntu Linux
: NOR crash
Target Milestone: ---
Assignee: kdevelop-bugs-null
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-07-27 08:01 UTC by Mattia Basaglia
Modified: 2020-08-29 04:33 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments
File I was editing (1.57 KB, text/x-c++hdr)
2020-07-27 08:01 UTC, Mattia Basaglia
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Mattia Basaglia 2020-07-27 08:01:18 UTC
Created attachment 130426 [details]
File I was editing

SUMMARY

It crashed a few times when I was writing the attached file, I left it in the state it was when it last crashed.

That file is part of a project, not sure that has something to do with it but it  only started crashing when I created this file


OBSERVED RESULT

The output says this:

OverflowError: Python int too large to convert to C long
kdevelop.plugins.clang: No parse session / AST attached to context for url QUrl("file:///(path to)/vector.hpp")
Segmentation fault (core dumped)

And crashes

EXPECTED RESULT

It shouldn't crash


SOFTWARE/OS VERSIONS
kdevelop 5.5.0

Operating System: Kubuntu 20.04
KDE Plasma Version: 5.18.5
KDE Frameworks Version: 5.68.0
Qt Version: 5.12.8
Kernel Version: 5.4.0-42-generic
OS Type: 64-bit
Processors: 8 × AMD FX(tm)-8320 Eight-Core Processor
Memory: 23.5 GiB of RAM
Comment 1 Milian Wolff 2020-07-30 08:49:33 UTC
can you attach the backtrace that you get when it crashes?

also note that it doesn't crash for me when I just load the file - so how do I reproduce it?
Comment 2 Bug Janitor Service 2020-08-14 04:33:10 UTC
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!
Comment 3 Bug Janitor Service 2020-08-29 04:33:08 UTC
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!