This is the mail archive of the gdb-patches@sourceware.org mailing list for the GDB project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: [PATCH 3/4] gdbserver: Ensure all debug output uses debug functions

From: Tom Tromey <tom at tromey dot com>
To: Alan Hayward <Alan dot Hayward at arm dot com>
Cc: "gdb-patches\@sourceware.org" <gdb-patches at sourceware dot org>, nd <nd at arm dot com>
Date: Tue, 16 Apr 2019 13:43:25 -0600
Subject: Re: [PATCH 3/4] gdbserver: Ensure all debug output uses debug functions
References: <20190416101729.16176-1-alan.hayward@arm.com> <20190416101729.16176-4-alan.hayward@arm.com>

>>>>> "Alan" == Alan Hayward <Alan.Hayward@arm.com> writes:

Alan> All debug output needs to go via debug functions to ensure it writes to the
Alan> correct output stream.

Alan> gdb/ChangeLog:

Alan> 2019-04-16  Alan Hayward  <alan.hayward@arm.com>

Alan> 	* nat/linux-waitpid.c (linux_debug): Call debug_vprintf.

Alan> gdb/gdbserver/ChangeLog:

Alan> 2019-04-16  Alan Hayward  <alan.hayward@arm.com>

Alan> 	* ax.c (ax_vdebug): Call debug_printf.
Alan> 	* debug.c (debug_write): New function.
Alan> 	* debug.h (debug_write): New declaration.
Alan> 	* linux-low.c (sigchld_handler): Call debug_write.

Thanks, this is ok.

Tom

References:
- [PATCH 0/4] gdbserver/testsuite : Capture gdbserver debug output during testing
  - From: Alan Hayward
- [PATCH 3/4] gdbserver: Ensure all debug output uses debug functions
  - From: Alan Hayward

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]