Bug 211069

Hi
- Is KSysGuard  crashing or not ?
Regards

Yes, crashing.
On this system I can't repport the full backtrace (not free space)

- Is this still happening with an updated KDE SC ?
Thanks

Same. And kbug is unable to provide bt:
Application: System Monitor (kdeinit4), signal: Segmentation fault
[Current thread is 0 (process 4889)]
I'm well in debuging mode. And the bt work for other application.

Sorry, I have the backtrace:
Application: System Monitor (kdeinit4), signal: Segmentation fault
[Current thread is 0 (LWP 8970)]

Thread 2 (Thread 0x7f9d89876910 (LWP 8971)):
#0  0x00007f9d93eded32 in select () from /lib/libc.so.6
#1  0x00007f9d976cc5a2 in QProcessManager::run (this=0xbd3590) at io/qprocess_unix.cpp:296
#2  0x00007f9d9760bca4 in QThreadPrivate::start (arg=0xbd3590) at thread/qthread_unix.cpp:188
#3  0x00007f9d973992b7 in start_thread (arg=<value optimized out>) at pthread_create.c:297
#4  0x00007f9d93ee57dd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112
#5  0x0000000000000000 in ?? ()

Thread 1 (Thread 0x7f9d97ba3740 (LWP 8970)):
[KCrash Handler]
#5  0x00007f9d97610b0f in QByteArray::nulTerminated (this=0xe96118) at tools/qbytearray.cpp:1418
#6  0x00007f9d97610bd8 in QByteArray::toDouble (this=0x39, ok=0x0) at tools/qbytearray.cpp:3393
#7  0x00007f9d8b81e159 in FancyPlotter::answerReceived (this=0xfd1790, id=100, answerlist=@0xd60fb8)
    at /var/tmp/portage/kde-base/ksysguard-4.3.4/work/ksysguard-4.3.4/ksysguard/gui/ksgrd/SensorClient.h:181
#8  0x00007f9d8b39d565 in KSGRD::SensorAgent::processAnswer (this=0xd60f90, buf=<value optimized out>, buflen=<value optimized out>)
    at /var/tmp/portage/kde-base/ksysguard-4.3.4/work/ksysguard-4.3.4/ksysguard/gui/ksgrd/SensorAgent.cc:184
#9  0x00007f9d8b3a41ee in KSGRD::SensorShellAgent::msgRcvd (this=0xd60f90) at /var/tmp/portage/kde-base/ksysguard-4.3.4/work/ksysguard-4.3.4/ksysguard/gui/ksgrd/SensorShellAgent.cc:91
#10 0x00007f9d8b3a5665 in KSGRD::SensorShellAgent::qt_metacall (this=0xd60f90, _c=QMetaObject::InvokeMetaMethod, _id=57, _a=0x7fff052c4900)
    at /var/tmp/portage/kde-base/ksysguard-4.3.4/work/ksysguard-4.3.4_build/ksysguard/gui/ksgrd/SensorShellAgent.moc:72
#11 0x00007f9d976fe03a in QMetaObject::activate (sender=0xd68f90, from_signal_index=<value optimized out>, to_signal_index=13, argv=0xfccac6) at kernel/qobject.cpp:3101
#12 0x00007f9d97695f02 in QProcessPrivate::_q_canReadStandardOutput (this=0xd6e250) at io/qprocess.cpp:564
#13 0x00007f9d97696461 in QProcess::qt_metacall (this=0xd68f90, _c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, _a=0x7fff052c4af0) at .moc/release-shared/moc_qprocess.cpp:101
#14 0x00007f9d96fda08e in KProcess::qt_metacall (this=0x7fff052c4330, _c=15294744, _id=33, _a=0xfccac6) at /var/tmp/portage/kde-base/kdelibs-4.3.4/work/kdelibs-4.3.4_build/kdecore/kprocess.moc:63
#15 0x00007f9d976fe03a in QMetaObject::activate (sender=0xd5aca0, from_signal_index=<value optimized out>, to_signal_index=4, argv=0xfccac6) at kernel/qobject.cpp:3101
#16 0x00007f9d97734cee in QSocketNotifier::activated (this=0x7fff052c4330, _t1=19) at .moc/release-shared/moc_qsocketnotifier.cpp:83
#17 0x00007f9d977045bb in QSocketNotifier::event (this=0xd5aca0, e=0x7fff052c50c0) at kernel/qsocketnotifier.cpp:316
#18 0x00007f9d94ab68d5 in QApplicationPrivate::notify_helper (this=0xbce970, receiver=0xd5aca0, e=0x7fff052c50c0) at kernel/qapplication.cpp:4065
#19 0x00007f9d94abe45a in QApplication::notify (this=0xbce870, receiver=0xd5aca0, e=0x7fff052c50c0) at kernel/qapplication.cpp:4030
#20 0x00007f9d95b2c5ea in KApplication::notify (this=0xbce870, receiver=0xd5aca0, event=0x7fff052c50c0) at /var/tmp/portage/kde-base/kdelibs-4.3.4/work/kdelibs-4.3.4/kdeui/kernel/kapplication.cpp:302
#21 0x00007f9d976ead2b in QCoreApplication::notifyInternal (this=0xbce870, receiver=0xd5aca0, event=0x7fff052c50c0) at kernel/qcoreapplication.cpp:606
#22 0x00007f9d97712939 in socketNotifierSourceDispatch (source=0xbd1590) at kernel/qcoreapplication.h:213
#23 0x00007f9d93542649 in IA__g_main_context_dispatch (context=0xbd1440) at gmain.c:1824
#24 0x00007f9d93545e68 in g_main_context_iterate (context=0xbd1440, block=1, dispatch=1, self=<value optimized out>) at gmain.c:2455
#25 0x00007f9d9354601e in IA__g_main_context_iteration (context=0xbd1440, may_block=1) at gmain.c:2518
#26 0x00007f9d9771264f in QEventDispatcherGlib::processEvents (this=0xbceba0, flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:327
#27 0x00007f9d94b45b28 in QGuiEventDispatcherGlib::processEvents (this=0x7fff052c4330, flags=<value optimized out>) at kernel/qguieventdispatcher_glib.cpp:202
#28 0x00007f9d976e9372 in QEventLoop::processEvents (this=<value optimized out>, flags={i = 86790880}) at kernel/qeventloop.cpp:149
#29 0x00007f9d976e955c in QEventLoop::exec (this=0x7fff052c5320, flags={i = 86790960}) at kernel/qeventloop.cpp:197
#30 0x00007f9d976eb99c in QCoreApplication::exec () at kernel/qcoreapplication.cpp:888
#31 0x00007f9d8b85abe4 in kdemain (argc=1, argv=0xbb97b0) at /var/tmp/portage/kde-base/ksysguard-4.3.4/work/ksysguard-4.3.4/ksysguard/gui/ksysguard.cc:579
#32 0x0000000000407719 in launch (argc=1, _name=0xb9bc58 "/usr/bin/ksysguard", args=<value optimized out>, cwd=0x0, envc=1, envs=0xb9bc7f "", reset_env=false, tty=0x0, avoid_loops=false, 
    startup_id_str=0xb9bc88 "amber.fw.local;1260172866;126176;8805_TIME114985") at /var/tmp/portage/kde-base/kdelibs-4.3.4/work/kdelibs-4.3.4/kinit/kinit.cpp:677
#33 0x0000000000407ebb in handle_launcher_request (sock=8, who=<value optimized out>) at /var/tmp/portage/kde-base/kdelibs-4.3.4/work/kdelibs-4.3.4/kinit/kinit.cpp:1169
#34 0x0000000000408359 in handle_requests (waitForPid=0) at /var/tmp/portage/kde-base/kdelibs-4.3.4/work/kdelibs-4.3.4/kinit/kinit.cpp:1362
#35 0x0000000000408f8d in main (argc=2, argv=0x7fff052c6458, envp=0x7fff052c6470) at /var/tmp/portage/kde-base/kdelibs-4.3.4/work/kdelibs-4.3.4/kinit/kinit.cpp:1793

> Thread 1 (Thread 0x7f9d97ba3740 (LWP 8970)):
> [KCrash Handler]
> #5  0x00007f9d97610b0f in QByteArray::nulTerminated (this=0xe96118) at
> tools/qbytearray.cpp:1418
> #6  0x00007f9d97610bd8 in QByteArray::toDouble (this=0x39, ok=0x0) at
> tools/qbytearray.cpp:3393

Hmm  this=0x39   is memory corruption afaics.

I'm not sur, beacause all work, execept this.
Memory test no repport failure.

After 9h of memtester + 2h of memtest86+ I can confirm that's the memory work.

This crash report is at least 3 years old and there were no further comments or status updates since then.

Therefore we believe that this crash is already fixed in recent KDE 4 versions or the backtrace is no longer applicable to the current KDE 4 sources.

If the crash still happens with a recent KDE version (4.10.5 or 4.11), please add an updated backtrace or provide steps to reproduce. For more information, see http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports

(To prevent automatic closing of this bug in the future, please set the bug status to ASSIGNED or CONFIRMED)

Closing, no new comments. Please reopen if you can still reproduce this bug.