[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-bugs-dist
Subject:    [Bug 73390] k3b crashs on start with "Der Wecker klingelt"
From:       Thomas Parth <deepfly () gmx ! net>
Date:       2004-01-25 0:15:22
Message-ID: 20040125001522.12749.qmail () ktown ! kde ! org
[Download RAW message or body]

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
      
http://bugs.kde.org/show_bug.cgi?id=73390      




------- Additional Comments From deepfly@gmx.net  2004-01-25 01:15 -------
i'm sorry for my ignorance but what exactly is a backtrace? 
(that's my first bug report at all and i'm only a user no linux programmer)

what i did in addition was to start k3b with strace
hope that helps a little bit =)
the last lines with sense
----------------------------------------------------
recvmsg(14, {msg_name(0)=NULL, msg_iov(1)=[{"s", 1}], msg_controllen=0, msg_flags=0}, 0) = 1
recvmsg(14, {msg_name(0)=NULL, msg_iov(1)=[{"\n", 1}], msg_controllen=0, msg_flags=0}, 0) = 1
close(14)                               = 0
fcntl64(16, F_SETFL, O_RDONLY|O_NONBLOCK) = 0
--- SIGSEGV (Segmentation fault) @ 0 (0) ---
rt_sigaction(SIGALRM, {SIG_DFL}, {SIG_DFL}, 8) = 0
alarm(3)                                = 0
sched_yield()                           = 0
---------------------------------------------------------
after this point its repeating endless times
   sched_yield()                           = 0
and a few times between
   nanosleep({0, 2000001}, NULL)           = 0
in the end it comes to this
---------------------------------------------------------
sched_yield()                           = 0
--- SIGALRM (Alarm clock) @ 0 (0) ---
+++ killed by SIGALRM +++
[prev in list] [next in list] [prev in thread] [next in thread]