Bug 167403 - knotifiy4 crashed and caused the signal 6
Summary: knotifiy4 crashed and caused the signal 6
Status: RESOLVED NOT A BUG
Alias: None
Product: kdelibs
Classification: Frameworks and Libraries
Component: knotify (show other bugs)
Version: 4.0
Platform: unspecified Linux
: NOR crash
Target Milestone: ---
Assignee: Olivier Goffart
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-07-25 08:26 UTC by mahmoudedreis
Modified: 2008-11-19 14:11 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description mahmoudedreis 2008-07-25 08:26:25 UTC
Version:           4.0 (using 4.0.3 (KDE 4.0.3), Kubuntu packages)
Compiler:          gcc
OS:                Linux (i686) release 2.6.24-19-generic

(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 0xb699f720 (LWP 5807)]
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[KCrash handler]
#6  0xb7f1f410 in __kernel_vsyscall ()
#7  0xb6f51085 in raise () from /lib/tls/i686/cmov/libc.so.6
#8  0xb6f52a01 in abort () from /lib/tls/i686/cmov/libc.so.6
#9  0xb6f9512c in ?? () from /lib/tls/i686/cmov/libc.so.6
#10 0xb6f9568c in realloc () from /lib/tls/i686/cmov/libc.so.6
#11 0xb4f0c27f in ?? () from /usr/lib/libxine.so.1
#12 0x2e726564 in ?? ()
Backtrace stopped: previous frame inner to this frame (corrupt stack?)
#0  0xb7f1f410 in __kernel_vsyscall ()
Comment 1 A. Spehr 2008-07-26 12:52:28 UTC
What were you doing when it crashed? 
We need a backtrace also:
http://techbase.kde.org/Contribute/Bugsquad/How_to_create_useful_crash_reports

You probably also want to upgrade first and see if it goes away. 

Thanks!
Comment 2 Christophe Marin 2008-11-19 14:11:27 UTC
No useful backtrace was provided (comment #1). Closing.