diff options
| author | Thiago Macieira <[email protected]> | 2025-05-14 14:19:24 -0700 |
|---|---|---|
| committer | Thiago Macieira <[email protected]> | 2025-05-19 14:46:36 -0700 |
| commit | 2da64908c250203c7d17031a6b5c1d769b6215a2 (patch) | |
| tree | 76e246376dfd82f48be3ef42c8adf6393870318b | |
| parent | a6070847f075296458e1afef0210f9c89aca4b2a (diff) | |
QTest::CrashHandler: ask GDB for the memory mapping layout on crash too
Processes usually crash due to invalid pointers, but sometimes it's hard
to know if a given value is valid or not just by eyeballing it. So let's
ask GDB to print it.
I don't think LLDB has a way to do it.
Pick-to: 6.9
Change-Id: I35e35bd3b79eeba49192fffd61474054cd089301
Reviewed-by: Edward Welbourne <[email protected]>
| -rw-r--r-- | src/testlib/qtestcrashhandler.cpp | 1 |
1 files changed, 1 insertions, 0 deletions
diff --git a/src/testlib/qtestcrashhandler.cpp b/src/testlib/qtestcrashhandler.cpp index a9a8b37884a..a89103028a2 100644 --- a/src/testlib/qtestcrashhandler.cpp +++ b/src/testlib/qtestcrashhandler.cpp @@ -360,6 +360,7 @@ void generateStackTrace() break; case Gdb: execlp("gdb", "gdb", "--nx", "--batch", "-ex", "thread apply all bt", + "-ex", "info proc mappings", "--pid", pidbuffer.array.data(), nullptr); break; case Lldb: |