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

List:       kde-devel
Subject:    Re: Alarm Clock Problem in LSongs
From:       Manuel Amador <rudd-o () amautacorp ! com>
Date:       2005-06-17 15:15:11
Message-ID: 1119021311.16403.30.camel () master ! amauta
[Download RAW message or body]

Then I'd suggest running the process under valgrind --tool=memcheck

That way you get a chance to fix mem corruption before it becomes a
problem.

El mié, 08-06-2005 a las 16:18 -0400, Michael Pyne escribió:
> On Wednesday 08 June 2005 07:54 am, Manuel Amador wrote:
> > SIGALRM is being signaled to your process.  This usually happens when
> > some code sets an alarm, the alarm gets triggered, and your app is not
> > handling signal SIGALRM.
> 
> In this case it is Qt itself that sets SIGALRM, but Qt's signal handler can't 
> run because of memory corruption leading to stack corruption.  gdb backtraces 
> from "Alarm clock" errors are quite funny to look at.
> 
> Regards,
>  - Michael Pyne
>  >> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
-- 
Manuel Amador                   <rudd-o@amautacorp.com>
http://www.amautacorp.com/            +593 (4) 220-7010
 
>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<

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