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

List:       kde-devel
Subject:    Re: strange crash
From:       Waldo Bastian <bastian () kde ! org>
Date:       2002-08-25 22:30:31
[Download RAW message or body]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Saturday 24 August 2002 09:01 pm, Christian Hubinger wrote:
> Hi!
>
> When my app crashes the console outup looks like:
>
> KCrash: crashing.... crashRecursionCounter = 2
> KCrash: Application Name = kmyfirewall path = <unknown> pid = 8007
> Alarm clock
>
> Whats the Alarm clock?

When your application crashes we try to start the crash-dialog but it can 
happen that your application deadlocks during that attempt. To handle that 
from happening we start a alarm: if your application then locks up it will be 
killed shortly after by the alarm.

The lock up happens when you crash inside malloc/free. malloc is protected 
with a mutex to guarantee that only one thread at a time can enter the malloc 
code, when you now crash inside malloc the crashhandler will deadlock the 
first time it tries to call malloc or free since it will wait for the mutex 
that was part of the original call to be freed, but that is not going to 
happen.

Cheers,
Waldo
- -- 
bastian@kde.org  |   SuSE Labs KDE Developer  |  bastian@suse.com
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQE9aVqHN4pvrENfboIRAmtVAKCU2g1AcgbyXEpa1h8zwHwKwe/5IQCgge4j
HwyyuVLSLySpTjh7HwGzjoM=
=Wm3b
-----END PGP SIGNATURE-----


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