Regarding the abnormal results arising when multiple planes are associated with an airport at the same time(after commit 89ec5c7)

[LShivaRudra]

I found one of the major causes of this issue. Check the following code snippet from airport.c(line 85):

In this, the msg_type is being set as 'msg->airport_num+10' which is same as the incoming msg type for the airport. So, there is a chance that the airport process will be receiving the data that it is sending. The same thing is happening in multiple other places of other files. So, using 'msg_type' attribute properly can fix the issue.

Also, it is better to use a specific msg_type to ATC process to receive data instead of using '0'. I plan to use '22' as the msg_type for ATC to receive msgs over the queue.

[LShivaRudra]

This issue seems to be solved to some extent after the commit "44c248b" of the 'sync_issues' branch.

The key changes are:

• Using a local copy ('Airport *local_airport) of the msg received through the queue and pass the copy to the thread routine function instead of using the received msg directly. This copy is then cleaned/de-allocated after use.
• The msg_type attribute of the msg_buf is properly used along with the parameters like 'departure_status' and 'arrival_status' making sure that the msgs sent by the airports are received by ATC only and vice-versa.

The working of this feature is as below: