diff options
| author | Joel Brobecker <brobecker@gnat.com> | 2013-06-11 10:20:24 +0000 |
|---|---|---|
| committer | Joel Brobecker <brobecker@gnat.com> | 2013-06-11 10:20:24 +0000 |
| commit | 0c3d84be3e696d2d1787a7240e086a72054b9679 (patch) | |
| tree | 01b984157999ba1865dcd834a8390c622fc832c0 /gdb/go-lang.c | |
| parent | 80e88e1aa2da7e516cfb7148fdd5d8777c2991dd (diff) | |
| download | gdb-0c3d84be3e696d2d1787a7240e086a72054b9679.zip gdb-0c3d84be3e696d2d1787a7240e086a72054b9679.tar.gz gdb-0c3d84be3e696d2d1787a7240e086a72054b9679.tar.bz2 | |
windows: Prefix thread ID values with "0x" in debug traces
The windows-nat.c debug traces print the thread ID in base 16,
but give no indication of it. So, in a trace like the following...
gdb: kernel event for pid=4816 tid=720 code=CREATE_THREAD_DEBUG_EVENT)
... where tid is "720", it's easy to be confused and think that
the thread ID is 720 rather than 0x720. This patch avoids the
confusion by adding the usual "0x" prefix used for hexadecimal
values.
gdb/ChangeLog:
* windows-nat.c (windows_continue): Add "0x" prefix for thread
ID in debug trace.
(get_windows_debug_event): Likewise, for all debug traces.
Diffstat (limited to 'gdb/go-lang.c')
0 files changed, 0 insertions, 0 deletions