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

List:       kde-devel
Subject:    Re: Help: How to debug an "Alarm clock" crash
From:       Anatoli Gorchetchnikov <anatoli () cns ! bu ! edu>
Date:       2005-01-27 9:13:34
Message-ID: 200501270413.34405.anatoli () cns ! bu ! edu
[Download RAW message or body]

On Thursday 27 January 2005 03:51, Boudewijn Rempt wrote:
> On Thursday 27 January 2005 09:32, Sebastian Trueg wrote:
> > Hi,
> >
> > I have this really annoying crash in K3b which causes an alarm clock. The
> > problem is that I don't know how to debug it. It does not occur when
> > running through gdb.
> > So the question is: what kind of error am I searching for when I get an
> > "Alarm clock"?
>
> A worse than usual error in memory management is what I usually do to get
> those erorrs: http://lists.kde.org/?l=kde-devel&m=106863190711786&w=2.

Yep. valgrind usually catches it easily.

-- 
Regards,

Anatoli
 
>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
[prev in list] [next in list] [prev in thread] [next in thread]