Bug 462455

Summary:	KDevelop crashed when added declaration of method and tried to switch to definition
Product:	[Applications] kdevelop	Reporter:	Piotr Mierzwinski <piotr.mierzwinski>
Component:	general	Assignee:	kdevelop-bugs-null
Status:	RESOLVED DUPLICATE
Severity:	crash	CC:	igorkuo
Priority:	NOR	Keywords:	drkonqi
Version First Reported In:	unspecified
Target Milestone:	---
Platform:	Neon
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:
Attachments:	New crash information added by DrKonqi

Description Piotr Mierzwinski 2022-11-30 19:25:29 UTC

Application: kdevelop (5.9.221170 (22.11.70))

Qt Version: 5.15.7
Frameworks Version: 5.101.0
Operating System: Linux 5.15.0-53-generic x86_64
Windowing System: X11
Distribution: KDE neon Unstable Edition
DrKonqi: 5.26.80 [CoredumpBackend]

-- Information about the crash:
I had opened 20 files. Opened one and added new method as public to mine class. I tried to switch to definition and KDevelop crashed.

The reporter is unsure if this crash is reproducible.

-- Backtrace (Reduced):
#6  std::__atomic_base<int>::load(std::memory_order) const (__m=std::memory_order_relaxed, this=0x3a) at /usr/include/c++/11/bits/atomic_base.h:479
#7  QAtomicOps<int>::loadRelaxed<int>(std::atomic<int> const&) (_q_value=<error reading variable: Cannot access memory at address 0x3a>) at ../../include/QtCore/../../src/corelib/thread/qatomic_cxx11.h:239
#8  QBasicAtomicInteger<int>::loadRelaxed() const (this=0x3a) at ../../include/QtCore/../../src/corelib/thread/qbasicatomic.h:107
#9  QWeakPointer<QObject>::internalData() const (this=0x5594d711ca40) at ../../include/QtCore/../../src/corelib/tools/qsharedpointer_impl.h:698
#10 QPointer<QObject>::data() const (this=0x5594d711ca40) at ../../include/QtCore/../../src/corelib/kernel/qpointer.h:77


Reported using DrKonqi

Comment 1 Piotr Mierzwinski 2022-11-30 19:25:30 UTC

Created attachment 154175 [details]
New crash information added by DrKonqi

DrKonqi auto-attaching complete backtrace.

Comment 2 Igor Kushnir 2022-12-01 06:53:31 UTC


*** This bug has been marked as a duplicate of bug 447740 ***