to add to the case, the debug logs just before that shows that the
next line which is done is creating a thread.
So a debug in that process creates the crash.
On 19.05.2007, at 01:04, Andreas Fink wrote:
folks,
I'm having an issue while using gwlib.
Under heavy load under multi CPU systems (intel and powerpc), We're
seeing the error "mutex_lock: Managed to lock the mutex twice!"
The issue is that it is being called by a normal debug() statement.
The only mutex lock generated in debug() is gwlist_lock(writers)
and I have so far not been able to figure out any theoretical
scenario where this could occur except when debug would call debug
again but this can not happen. It can call panic under some rare
scenario which would then lock again but we already fixed that by
having panic not considering locking writers (there's no point as
we will exit afterwards immediately anyway).
Anyone have a hint?
Andreas Fink
Fink Consulting GmbH
Global Networks Schweiz AG
BebbiCell AG
---------------------------------------------------------------
Tel: +41-61-6666330 Fax: +41-61-6666331 Mobile: +41-79-2457333
Address: Clarastrasse 3, 4058 Basel, Switzerland
E-Mail: [EMAIL PROTECTED]
www.finkconsulting.com www.global-networks.ch www.bebbicell.ch
---------------------------------------------------------------
ICQ: 8239353 MSN: [EMAIL PROTECTED] AIM: smsrelay Skype: andreasfink
Yahoo: finkconsulting SMS: +41792457333
Andreas Fink
Fink Consulting GmbH
Global Networks Schweiz AG
BebbiCell AG
---------------------------------------------------------------
Tel: +41-61-6666330 Fax: +41-61-6666331 Mobile: +41-79-2457333
Address: Clarastrasse 3, 4058 Basel, Switzerland
E-Mail: [EMAIL PROTECTED]
www.finkconsulting.com www.global-networks.ch www.bebbicell.ch
---------------------------------------------------------------
ICQ: 8239353 MSN: [EMAIL PROTECTED] AIM: smsrelay Skype: andreasfink
Yahoo: finkconsulting SMS: +41792457333
