Message: previous - next
Month: January 2015

Re: [trinity-users] R14 Kpilot and KOrganizer Reminder Daemon Problems.

From: Will Hill <will.hillnotes@...>
Date: Thu, 8 Jan 2015 17:44:36 -0600
On Thursday 08 January 2015, Timothy Pearson wrote:
> Sounds like a serious bug; can you file a report on our bugtracker so that
> we don't lose track of this?
> Something you can do in the meantime is to install the kpilot debugging
> symbols along with tdelibs-trinity-dbg, then when the daemon goes into its
> CPU loop do the following:
> 1.) Get the PID of the process consuming all the CPU (use top or similar)
> 2.) gdb --pid <pid obtained above>
> 3.) thread apply all bt
> Once that is done post the output on the bug report; we'll be able to tell
> what's going wrong fairly readily.

That's the sort advice I was looking for, thank you.  

[long list of symbols found and not found, all TDE seem to be found]
TQGListIterator::operator++ (this=0xbfb0dd08) at tools/qglist.cpp:1524
1524    tools/qglist.cpp: No such file or directory.
(gdb) thread apply all bt

Thread 2 (Thread 0xb54afb70 (LWP 24717)):
#0  0xb778c424 in __kernel_vsyscall ()
#1  0xb6b35733 in pthread_cond_timedwait@@GLIBC_2.3.2 ()
   from /lib/i386-linux-gnu/i686/cmov/
#2  0xb71996a0 in thread_sleep (ti=ti@entry=0xb54af288) at 
#3  0xb7199be4 in TQThread::sleep (secs=2) at kernel/qthread_unix.cpp:273
#4  0xb76ff34c in DeviceCommThread::run() () 
from /opt/trinity/lib/
#5  0xb7199937 in TQThreadInstance::start (_arg=0x9241c8c)
    at kernel/qthread_unix.cpp:142
#6  0xb6e7deb3 in ?? () from /lib/i386-linux-gnu/
#7  0xb6b30c39 in start_thread () 
from /lib/i386-linux-gnu/i686/cmov/
#8  0xb5e199fe in clone () from /lib/i386-linux-gnu/i686/cmov/

Thread 1 (Thread 0xb5668710 (LWP 24716)):
#0  TQGListIterator::operator++ (this=0xbfb0dd08) at tools/qglist.cpp:1524
---Type <return> to continue, or q <return> to quit---

I'm not sure what that means, but there is is.  I'll sign up for an account on 
your bug tracker and post more there later, thank you.  

Where can I find the full build log?