Gilles Peskine via mbed-tls mbed-tls@lists.trustedfirmware.org wrote: > If GDB isn't breaking on any aesni_setkey_enc_128 calls from the TLS code, I > can think of two explanations. One is that the compiler has inlined several > copies of this function and GDB is only breaking on one of the > copies.
GDB is pretty good about getting them all (with the right data from the compiler).
> Another is that TLS might not be using AES-128 after all — maybe it's > using AES-256 or Chacha-Poly? Please double-check which cipher suite is used, > e.g. with debugging traces or Wireshark.
This seems more likely.