What's the use of NRF_MESH_ASSERT_DEBUG(*p_flags & MESH_CONFIG_ENTRY_FLAG_BUSY);?

RE: What's the use of NRF_MESH_ASSERT_DEBUG(*p_flags & MESH_CONFIG_ENTRY_FLAG_BUSY);?

Joakim Jakobsen — Wed, 09 Jun 2021 10:29:23 GMT

You are correct about this only beeing triggered in debug mode.

Glad you worked around it. I'll see if I can track down the root cause of this.

Br,
Joakim

RE: What's the use of NRF_MESH_ASSERT_DEBUG(*p_flags & MESH_CONFIG_ENTRY_FLAG_BUSY);?

rmarques — Mon, 07 Jun 2021 11:29:19 GMT

The Segger file editor does not identify NDEBUG being added when building the stack in release mode though. At least it grays out the first ifdef and not the else, so I don't know. I managed to go around the problem in the meanwhile though.

RE: What's the use of NRF_MESH_ASSERT_DEBUG(*p_flags & MESH_CONFIG_ENTRY_FLAG_BUSY);?

rmarques — Mon, 07 Jun 2021 11:24:14 GMT

Sorry, I think I was not notified of this answer. This only happened sometimes but always in debug mode. I think it is a feature of the function not being triggered in release mode. Check here, line 80 of nrf_mesh_assert.h:

/**
* Run-time assertion for debug use.
* Debug assertions are only run if the stack is compiled in debug mode.
*/
#ifdef NDEBUG /* The NDEBUG define is added automatically when compiling in release mode. */
#define NRF_MESH_ASSERT_DEBUG(cond) (void) (cond)
#else
#define NRF_MESH_ASSERT_DEBUG(cond) NRF_MESH_ASSERT(cond)
#endif

RE: What's the use of NRF_MESH_ASSERT_DEBUG(*p_flags & MESH_CONFIG_ENTRY_FLAG_BUSY);?

Joakim Jakobsen — Thu, 27 May 2021 21:01:33 GMT

This doesn't happen every time in debug mode either?

RE: What's the use of NRF_MESH_ASSERT_DEBUG(*p_flags & MESH_CONFIG_ENTRY_FLAG_BUSY);?

Joakim Jakobsen — Thu, 27 May 2021 21:00:40 GMT

Strange that this only occurs in debug mode.

I'll take a closer look and get back to you.

Br,
Joakim