Bug 414556 - Kdevelop crashed when changing environment variables for make
Summary: Kdevelop crashed when changing environment variables for make
Status: RESOLVED WORKSFORME
Alias: None
Product: kdevelop
Classification: Applications
Component: general (show other bugs)
Version: 5.4.4
Platform: openSUSE Linux
: NOR crash
Target Milestone: ---
Assignee: kdevelop-bugs-null
URL:
Keywords: drkonqi
Depends on:
Blocks:
 
Reported: 2019-11-27 02:19 UTC by Aaron Williams
Modified: 2022-10-30 05:04 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments
New crash information added by DrKonqi (200.54 KB, text/plain)
2019-11-27 02:19 UTC, Aaron Williams
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Aaron Williams 2019-11-27 02:19:08 UTC
Application: kdevelop (5.4.4)

Qt Version: 5.13.1
Frameworks Version: 5.64.0
Operating System: Linux 4.12.14-lp151.28.32-default x86_64
Distribution: "openSUSE Leap 15.1"

-- Information about the crash:
My old project file got trashed so I was recreating one. When I changed the environment variable group while the background parser was going it crashed. Kdevelop seems to frequently trash the project files.

-- Backtrace (Reduced):
#7  __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:51
#8  0x00007f541145a741 in __GI_abort () at abort.c:79
#9  0x00007f5411bfa09b in qt_message_fatal (context=..., message=<synthetic pointer>...) at global/qlogging.cpp:1907
#10 QMessageLogger::fatal (this=this@entry=0x7fffb5bbcad0, msg=msg@entry=0x7f53cb3e3b00 "you need to call MakeBuilderSettings::instance before using") at global/qlogging.cpp:888
#11 0x00007f53cb3e104b in MakeBuilderSettings::self () at /usr/src/debug/kdevelop5-5.4.4-lp151.73.1.x86_64/build/plugins/makebuilder/makebuilderconfig.cpp:26


Possible duplicates by query: bug 413943, bug 413708, bug 412300, bug 412218, bug 411017.

Reported using DrKonqi
Comment 1 Aaron Williams 2019-11-27 02:19:10 UTC
Created attachment 124132 [details]
New crash information added by DrKonqi

DrKonqi auto-attaching complete backtrace.
Comment 2 Justin Zobel 2022-09-30 04:37:59 UTC
Thank you for reporting this crash in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the crash with a recent software version?

If you can reproduce the issue, please change the status to "CONFIRMED" when replying. Thank you!
Comment 3 Bug Janitor Service 2022-10-15 04:55:35 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 4 Bug Janitor Service 2022-10-30 05:04:07 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!