Bug 188697 - SIGSEGV signal 11 Crash of application
Summary: SIGSEGV signal 11 Crash of application
Status: RESOLVED WORKSFORME
Alias: None
Product: KSystemLog
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Ubuntu Unspecified
: NOR crash
Target Milestone: ---
Assignee: Nicolas Ternisien
URL:
Keywords: investigated, triaged
Depends on:
Blocks:
 
Reported: 2009-04-03 00:33 UTC by André
Modified: 2018-10-21 05:09 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description André 2009-04-03 00:33:11 UTC
Version:            (using KDE 4.2.2)
Installed from:    Ubuntu Packages

KDE 4.2.2 

Ksystemlog was opnened for many hours, tried to open Kernel protocol, it reloaded at around 20 % several times, then crashed the application.


Anwendung: KSystemlog (ksystemlog), Signal SIGSEGV
[Current thread is 0 (LWP 13903)]

Thread 2 (Thread 0xb4472b90 (LWP 13984)):
#0  0xb8005430 in __kernel_vsyscall ()
#1  0xb68f5df1 in select () from /lib/tls/i686/cmov/libc.so.6
#2  0xb7514150 in ?? () from /usr/lib/libQtCore.so.4
#3  0xb74446ae in ?? () from /usr/lib/libQtCore.so.4
#4  0xb657d50f in start_thread () from /lib/tls/i686/cmov/libpthread.so.0
#5  0xb68fda0e in clone () from /lib/tls/i686/cmov/libc.so.6

Thread 1 (Thread 0xb618d6c0 (LWP 13903)):
[KCrash Handler]
#6  0x080cd3a6 in _start ()
Comment 1 Dario Andres 2009-05-08 00:07:26 UTC
If you experience this regularly, may you read http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports and post a complete backtrace here? Thanks
Comment 2 Dario Andres 2009-06-26 16:34:04 UTC
Marking as NEEDSINFO
Comment 3 Andrew Crouthamel 2018-09-19 04:38:49 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 Andrew Crouthamel 2018-10-21 05:09:32 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!