diff options
| author | Tom Tromey <tromey@adacore.com> | 2020-04-15 12:37:29 -0600 |
|---|---|---|
| committer | Tom Tromey <tromey@adacore.com> | 2020-04-15 12:49:05 -0600 |
| commit | ce127a96c912965e0fe24906d6083e5e9c79a92f (patch) | |
| tree | a5284c651b043f67b3d290025beb2cab688d5a91 /libiberty/xvasprintf.c | |
| parent | 99f1bc6aaa2810fa4600b1cfd13d2d52678e1a66 (diff) | |
| download | binutils-ce127a96c912965e0fe24906d6083e5e9c79a92f.zip binutils-ce127a96c912965e0fe24906d6083e5e9c79a92f.tar.gz binutils-ce127a96c912965e0fe24906d6083e5e9c79a92f.tar.bz2 | |
Use debug_printf in windows-nat.c
While debugging a bug on Windows, I noticed that windows-nat.c is not
sending its debugging output to gdb_stdlog. This is unfortunate
because it means that "set logging debugredirect" doesn't work
properly.
This patch fixes the problem by changing windows-nat.c to use
debug_printf.
Note that get_windows_debug_event also writes one debugging message
unconditionally. It isn't clear to me if this really ought to use
DEBUG_EVENTS or not, since it seems like perhaps it is intended to
note an unexpected event occurring. So, I didn't change this.
I'm checking this in.
gdb/ChangeLog
2020-04-15 Tom Tromey <tromey@adacore.com>
* windows-nat.c (DEBUG_EXEC, DEBUG_EVENTS, DEBUG_MEM)
(DEBUG_EXCEPT): Use debug_printf.
Diffstat (limited to 'libiberty/xvasprintf.c')
0 files changed, 0 insertions, 0 deletions