[PATCH 0/3] [gdb] Fix backtrace in log file

[Tom de Vries <tdevries@suse.de>]

This series contains three patches.

The first and last fix a problem with the backtrace not showing up in log
files, one for libbacktrace and one for execinfo.

The second drops an unnecessary flush.

An earlier attempt was submitted here [1], which tried to fix the problem by
adding a logging_file::fd.  This series tries to follow up on review comments.

Tested on x86_64-linux.

Also tested the added test-case with --disable-libbacktrace.

[1] https://sourceware.org/pipermail/gdb-patches/2026-October/231239.html

Tom de Vries (3):
  [gdb] Fix backtrace in log file (libbacktrace case)
  [gdb] Don't flush in handle_fatal_signal
  [gdb] Fix backtrace in log file (execinfo case)

 gdb/bt-utils.c                                | 21 ++++--
 gdb/cli/cli-logging.c                         | 22 +++++-
 gdb/event-top.c                               |  8 --
 gdb/logging-file.h                            |  3 +-
 gdb/mi/mi-console.c                           |  7 +-
 gdb/mi/mi-console.h                           |  2 +-
 .../gdb.base/logging-internal-error.exp       | 75 +++++++++++++++++++
 gdb/ui-file.c                                 | 17 +----
 gdb/ui-file.h                                 | 36 +++++++--
 9 files changed, 147 insertions(+), 44 deletions(-)
 create mode 100644 gdb/testsuite/gdb.base/logging-internal-error.exp


base-commit: 21cffe7c0955c6bdb0c14ded96939d409f3c21f0
-- 
2.51.0