Bug 379159

Summary:	debugging
Product:	[Developer tools] kcachegrind	Reporter:	heiko stark <m7sthe>
Component:	general	Assignee:	Josef Weidendorfer <josef.weidendorfer>
Status:	RESOLVED WORKSFORME
Severity:	crash	CC:	heiko
Priority:	NOR	Keywords:	drkonqi
Version First Reported In:	0.7.4kde
Target Milestone:	---
Platform:	Mageia RPMs
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description heiko stark 2017-04-24 12:36:41 UTC

Application: kcachegrind (0.7.4kde)
KDE Platform Version: 4.14.30
Qt Version: 4.8.6
Operating System: Linux 4.4.59-desktop-1.mga5 x86_64
Distribution: "Mageia 5"

-- Information about the crash:
- What I was doing when the application crashed:

Clicking onto specific functions in "Aufrufliste nach Höchstkosten"

-- Backtrace:
Application: KCachegrind (kcachegrind), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[KCrash Handler]
#5  0x00000000004903d5 in InstrView::doUpdate(int, bool) ()
#6  0x00007fe345c5f88a in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () at /lib64/libQtCore.so.4
#7  0x00007fe345c63c2b in QObject::event(QEvent*) () at /lib64/libQtCore.so.4
#8  0x00007fe3468cd79c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /lib64/libQtGui.so.4
#9  0x00007fe3468d3e40 in QApplication::notify(QObject*, QEvent*) () at /lib64/libQtGui.so.4
#10 0x00007fe34760040a in KApplication::notify(QObject*, QEvent*) () at /lib64/libkdeui.so.5
#11 0x00007fe345c4bcad in QCoreApplication::notifyInternal(QObject*, QEvent*) () at /lib64/libQtCore.so.4
#12 0x00007fe345c7b31b in QTimerInfoList::activateTimers() () at /lib64/libQtCore.so.4
#13 0x00007fe345c784c1 in timerSourceDispatch(_GSource*, int (*)(void*), void*) () at /lib64/libQtCore.so.4
#14 0x00007fe342530c6d in g_main_context_dispatch () at /lib64/libglib-2.0.so.0
#15 0x00007fe342530f18 in g_main_context_iterate.isra () at /lib64/libglib-2.0.so.0
#16 0x00007fe342530fbc in g_main_context_iteration () at /lib64/libglib-2.0.so.0
#17 0x00007fe345c78e1e in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /lib64/libQtCore.so.4
#18 0x00007fe34696b4f6 in QGuiEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /lib64/libQtGui.so.4
#19 0x00007fe345c4a931 in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /lib64/libQtCore.so.4
#20 0x00007fe345c4ac45 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at /lib64/libQtCore.so.4
#21 0x00007fe345c4fe59 in QCoreApplication::exec() () at /lib64/libQtCore.so.4
#22 0x000000000041e74e in main ()

Reported using DrKonqi

Comment 1 Josef Weidendorfer 2017-04-25 17:13:42 UTC

The backtrace is not enough for me to understand/reproduce the issue.
I only see that the machine code view was requested to be updated before crashing.

Is this reproducable for you? Any chance to send me the profile data which triggers the crash by private email?

Comment 2 Heiko Stark 2017-04-26 07:21:25 UTC

I'm sorry, I have delete this profile data. So, I hope another one find the same bug.

Best regards,
Heiko

Comment 3 Justin Zobel 2020-12-17 05:28:25 UTC

Thank you for the crash report.

As it has been a while since this was reported, can you please test and confirm if this issue is still occurring or if this bug report can be marked as resolved.

I have set the bug status to "needsinfo" pending your response, please change back to "reported" or "resolved/worksforme" when you respond, thank you.

Comment 4 Heiko Stark 2020-12-17 20:15:06 UTC

Since the error did not occur again in my case and no one else found it, I think this issue can be closed.

Best regards,
Heiko

Comment 5 Bug Janitor Service 2021-01-01 04:36:44 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 6 Christoph Feck 2021-01-09 16:23:50 UTC

Thanks for the update; changing status.