Use %x when printing the TID
One spot in windows-nat.c uses %ld to print the TID, but all other spots use %x, as does the infrun logging. This makes it unnecessarily hard to tell which other log messages correspond to this one. This patch changes the one outlier to use %x. gdb/ChangeLog 2019-10-15 Tom Tromey <tromey@adacore.com> * windows-nat.c (windows_nat_target::resume): Use %x when logging TID. Change-Id: Ic66efeb8a7ec08e7fb007320318f51acbf976734
This commit is contained in:
parent
96b49c5ec0
commit
55dfc88f7e
|
@ -1,3 +1,8 @@
|
|||
2019-10-15 Tom Tromey <tromey@adacore.com>
|
||||
|
||||
* windows-nat.c (windows_nat_target::resume): Use %x when logging
|
||||
TID.
|
||||
|
||||
2019-10-15 Tom Tromey <tromey@adacore.com>
|
||||
|
||||
* windows-nat.c (windows_nat_target::fetch_registers)
|
||||
|
|
|
@ -1447,8 +1447,8 @@ windows_nat_target::resume (ptid_t ptid, int step, enum gdb_signal sig)
|
|||
|
||||
last_sig = GDB_SIGNAL_0;
|
||||
|
||||
DEBUG_EXEC (("gdb: windows_resume (pid=%d, tid=%ld, step=%d, sig=%d);\n",
|
||||
ptid.pid (), ptid.tid (), step, sig));
|
||||
DEBUG_EXEC (("gdb: windows_resume (pid=%d, tid=0x%x, step=%d, sig=%d);\n",
|
||||
ptid.pid (), (unsigned) ptid.tid (), step, sig));
|
||||
|
||||
/* Get context for currently selected thread. */
|
||||
th = thread_rec (inferior_ptid.tid (), FALSE);
|
||||
|
|
Loading…
Reference in New Issue