From: Daniel Jacobowitz <drow@false.org>
To: Pedro Alves <pedro_alves@portugalmail.pt>
Cc: gdb-patches@sourceware.org
Subject: Re: [gdbserver/win32]: Ignore OUTPUT_DEBUG_STRING_EVENT events when remote is not connected.
Date: Sun, 08 Jul 2007 03:48:00 -0000 [thread overview]
Message-ID: <20070708034833.GA18642@caradoc.them.org> (raw)
In-Reply-To: <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
next prev parent reply other threads:[~2007-07-08 3:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-08 1:22 Pedro Alves
2007-07-08 3:48 ` Daniel Jacobowitz [this message]
2007-07-08 14:45 ` Pedro Alves
2007-07-08 17:22 ` Daniel Jacobowitz
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20070708034833.GA18642@caradoc.them.org \
--to=drow@false.org \
--cc=gdb-patches@sourceware.org \
--cc=pedro_alves@portugalmail.pt \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox