Bug 403677

Summary:	kdevelop crash when wrong completion on include
Product:	[Applications] kdevelop	Reporter:	jd.frattini
Component:	Code completion	Assignee:	kdevelop-bugs-null
Status:	RESOLVED WORKSFORME
Severity:	crash	CC:	jd.frattini, justin.zobel
Priority:	NOR
Version First Reported In:	5.3.1
Target Milestone:	---
Platform:	Debian testing
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description jd.frattini 2019-01-28 06:50:51 UTC

Kdevelop crashes when using completion to resolve include filename but not a header was choosed by the completion.
Reproducible: always.


STEPS TO REPRODUCE
Have a Makefile in the header directory
Have a header file starting by the letter m
Start a #include statement
Start to write the path
Once the completion is in the right header directory, choose m
Kdevelop will give priority to Makefile
Type enter, Makefile will be written as the header file name
And just next, kdevelop will crash

OBSERVED RESULT
Crash


EXPECTED RESULT
No crash

As other issues with kdevelop, it seems the problem comes from the parser. But I cannot ensure this last point.

Comment 1 Justin Zobel 2021-06-20 08:34:44 UTC

As this crash is quite old now, can you please confirm if this crash still occurs on a current version?

If the crash does still occur can you please provide a backtrace to make diagnosing the issue easier for the developers. Instructions on how to provide one are available here: https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports

This bug has been set to "NEEDSINFO/WAITINGFORINFO", if you are able to update the bug report please mark it as reported when you add the new information, thank you.

Comment 2 Bug Janitor Service 2021-07-05 04:33:51 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 2021-07-20 04:33:42 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!