5B4AIT Calendar

May 2012
M T W T F S S
« Apr   Jun »
 123456
78910111213
14151617181920
21222324252627
28293031  

HamSphere Forums

HamSphere info

Yahoo! Weather Forecasts

Cyprus Mail News

Daily Archives: May 18, 2012 08:57

Debugging ready

Hi. After like 2 days of debugging I could pinpoint the problem to a mutex variable that was accessed outside a mutex lock = memory violation and failure.

Say that you have  a MUTUAL EXCLUSIVE variable called rmut in a multi threaded environment

Before you do an operation you invike mutex_lock then you do some stuff and finally unlock the variable.

pthread_mutex_lock(&rmut);

…do something clever …

pthread_mutex_unlock(&rmut);

I realized that I had forgotten to lock one memory area in the logon procedure resulting in memory violation error.

Servers have been up for almost 48 hours without any stops. I think I have solved it.

73

Kelly

 

 

Solar-Terrestrial Data

free counters

IP address

Tag Cloud