Searched refs:overflowed (Results 1 – 22 of 22) sorted by relevance
63 if (st->overflowed) { in base64_outch()68 st->overflowed = true; in base64_outch()156 builder->overflowed = true; in jwt_add_header()201 return builder->overflowed ? -ENOMEM : 0; in jwt_sign()211 builder->overflowed = false; in jwt_init_builder()
46 bool overflowed : 1; member140 data->overflowed = false; in mcux_pwt_enable_capture()229 data->overflowed |= u32_add_overflow(1, in mcux_pwt_isr()232 data->overflowed |= u32_add_overflow(1, in mcux_pwt_isr()262 if (data->overflowed) { in mcux_pwt_isr()274 data->overflowed = false; in mcux_pwt_isr()
47 bool overflowed; member
50 zassert_equal(build.overflowed, false, "Not overflow"); in ZTEST()
36 alternate_thread: Input string is too long and stack overflowed!
347 const bool overflowed = write_index < old_write_index; in stream_cb() local366 if (read_idx < write_index || (overflowed && read_idx < write_index)) { in stream_cb()
82 bounds of the current process stack are overflowed. This is done
73 bounds of the current process stack are overflowed. This is done
218 the stack actually overflowed.226 that the entire stack buffer has overflowed, but instead that the current
197 the bounds of the current process stack are overflowed. This is done
210 if the bounds of the current process stack are overflowed.
242 if the bounds of the current process stack are overflowed.
322 * ``ZEP-1130`` - region 'RAM' overflowed occurs while building test_hmac_prng
311 * ``ZEP-2378`` - sample/bluetooth/ipsp: When build the app 'ROM' overflowed
1522 * :github:`29327` - mec15xxevb_assy6853:region ``SRAM`` overflowed during build
2335 * :github:`46684` - ethernet: w5500: driver will be stack overflowed when reading the invalid(corru…
3382 * :github:`51421` - tests: net: socket: tls: net.socket.tls region ``FLASH`` overflowed
52 catches issues when the entire stack buffer has overflowed, and not
574 overflowed.
927 "External SPIRAM overflowed.")
1006 "External SPIRAM overflowed.")
1014 "External SPIRAM overflowed.")
