I found a multi-thread safety issue in mesh stack code and it still exist
in the newest version.
When "seg_ack" was called by callout module, there was anthoer thread which
receive mesh datas was calling "seg_rx_reset()" and set the "rx->sub" to NULL,
then "seg_ack" called "send_ack" and acess the rx->sub->net_idx, so it crashed.
The adv-sending task and ble-data-receiving task and each "callout" are not
in the same thread, why don't you add the Multi-thread protection mechanism in
mesh stack? or something I used the wrong way?
Waiting for your replies! thank you so much!
[ Full content available at: https://github.com/apache/mynewt-nimble/issues/199
]
This message was relayed via gitbox.apache.org for [email protected]
