This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [gdbserver/win32]: Ignore OUTPUT_DEBUG_STRING_EVENT events when remote is not connected.
- From: Daniel Jacobowitz <drow at false dot org>
- To: Pedro Alves <pedro_alves at portugalmail dot pt>
- Cc: gdb-patches at sourceware dot org
- Date: Sat, 7 Jul 2007 23:48:33 -0400
- Subject: Re: [gdbserver/win32]: Ignore OUTPUT_DEBUG_STRING_EVENT events when remote is not connected.
- References: <4690375A.6030009@portugalmail.pt>
On Sun, Jul 08, 2007 at 02:01:14AM +0100, Pedro Alves wrote:
> Hi,
>
> OUTPUT_DEBUG_STRING_EVENT events can happen from after the inferior
> is created, until it is stopped at the initial breakpoint, waiting
> for gdb. The OUTPUT_DEBUG_STRING_EVENT handler doesn't currently
> check if a remote connection is open before sending data, generating
> annoying putpkt error logs to gdbserver's console. This
> patch fixes it by simply ignoring those events when there isn't any
> gdb connected yet. I didn't use server_wait, because this event
> is also handled in win32_kill, outside of a wait.
But don't you want to discard it if you're outside of a wait? I don't
see how GDB would display them otherwise; remote_wait handles the 'O'
response.
--
Daniel Jacobowitz
CodeSourcery