From 75700d9f7ffc6eef2ee4c4ebcab9b2c46b5c76de Mon Sep 17 00:00:00 2001
From: Roman Zeyde <roman.zeyde@satoshilabs.com>
Date: Thu, 17 Apr 2025 11:21:59 +0300
Subject: [PATCH] fix(core): dump allocated QSTRs also in debug firmware

Otherwise, it's hard to understand which QSTR causes the assertion error.

[no changelog]
---
 core/embed/upymod/modtrezorutils/modtrezorutils.c | 2 --
 1 file changed, 2 deletions(-)

diff --git a/core/embed/upymod/modtrezorutils/modtrezorutils.c b/core/embed/upymod/modtrezorutils/modtrezorutils.c
index 389187035d..5799f9ac07 100644
--- a/core/embed/upymod/modtrezorutils/modtrezorutils.c
+++ b/core/embed/upymod/modtrezorutils/modtrezorutils.c
@@ -329,9 +329,7 @@ STATIC mp_obj_t mod_trezorutils_check_heap_fragmentation(void) {
   size_t n_pool, n_qstr, n_str_data_bytes, n_total_bytes;
   qstr_pool_info(&n_pool, &n_qstr, &n_str_data_bytes, &n_total_bytes);
   if (n_pool) {
-#ifdef TREZOR_EMULATOR
     qstr_dump_data();
-#endif
     mp_raise_msg_varg(&mp_type_AssertionError,
                       "Runtime QSTR allocation: " UINT_FMT " pools, " UINT_FMT
                       " strings, " UINT_FMT " data bytes, " UINT_FMT