Fix gdbserver/linux target_waitstatus logging assert
authorPedro Alves <pedro@palves.net>
Fri, 18 Feb 2022 16:42:06 +0000 (16:42 +0000)
committerPedro Alves <pedro@palves.net>
Thu, 10 Mar 2022 11:35:53 +0000 (11:35 +0000)
commite48359eaa8c4c79a40a21726c9fa823241793b1e
tree0722b8ca6d87246bd7eb57efbabe43a931219a91
parentbed566bbf6b619e15f0290c7d4c8a8b6dcbd99d4
Fix gdbserver/linux target_waitstatus logging assert

Turning on debug output in gdbserver leads to an assertion failure if
gdbserver reports a non-signal event:

    [threads] wait_1: LWP 3273770: extended event with waitstatus status->kind = EXECD, execd_pathname = gdb.threads/non-ldr-exc-1/non-ldr-exc-1
    [threads] wait_1: Hit a non-gdbserver trap event.
  ../../src/gdbserver/../gdb/target/waitstatus.h:365: A problem internal to GDBserver has been detected.
  sig: Assertion `m_kind == TARGET_WAITKIND_STOPPED || m_kind == TARGET_WAITKIND_SIGNALLED' failed.

Fix it in the obvious way, using target_waitstatus::to_string(),
resulting in, for example:

  [threads] wait_1: ret = LWP 1542412.1542412, status->kind = STOPPED, sig = GDB_SIGNAL_TRAP

Change-Id: Ia4832f9b4fa39f4af67fcaf21fd4d909a285a645
gdbserver/linux-low.cc