diff options
| author | Simon Marchi <simon.marchi@efficios.com> | 2021-10-28 11:25:45 -0400 |
|---|---|---|
| committer | Simon Marchi <simon.marchi@efficios.com> | 2021-10-28 11:25:45 -0400 |
| commit | 0fab795564847898adec8436f068ed6089876713 (patch) | |
| tree | 48570993c043dfbcb0943f76db28b0a3f4af5a03 /gdb/or1k-linux-nat.c | |
| parent | c0492bea7ca33fafc280f08f4ed9f505d29e7130 (diff) | |
| download | binutils-0fab795564847898adec8436f068ed6089876713.zip binutils-0fab795564847898adec8436f068ed6089876713.tar.gz binutils-0fab795564847898adec8436f068ed6089876713.tar.bz2 | |
gdb: use ptid_t::to_string in infrun debug messages
In debug messages, I think it would be more helpful to print ptid using
the simple "pid.lwp.tid" notation in infrun debug messages. I am
currently debugging some fork issues, and find the pid_to_str output not
so useful, as it doesn't tell which process a thread belongs to.
It currently shows up like this:
[infrun] resume_1: step=1, signal=GDB_SIGNAL_0, trap_expected=0, current thread [Thread 0x7ffff7d95740 (LWP 892942)] at 0x55555555521f
With the patch, it shows up like this:
[infrun] resume_1: step=1, signal=GDB_SIGNAL_0, trap_expected=1, current thread [894072.894077.0] at 0x5555555551d9
Change-Id: I130796d7dfb0d8e763b8358d8a6002701d80c4ea
Diffstat (limited to 'gdb/or1k-linux-nat.c')
0 files changed, 0 insertions, 0 deletions