Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Pedro Alves <pedro@codesourcery.com>
To: Doug Evans <dje@google.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [RFA] Fix gdbserver queued packet handling
Date: Mon, 03 May 2010 20:41:00 -0000	[thread overview]
Message-ID: <201005032141.36926.pedro@codesourcery.com> (raw)
In-Reply-To: <AANLkTikcoyGrTjyg2qk2stIVQ2pymhD-_mxUc3xcVfAx@mail.gmail.com>

On Monday 03 May 2010 20:53:14, Doug Evans wrote:

> P.S. IWBN if one didn't have to continually keep bringing stuff over
> from gdb.  Wouldn't it be nice if one could just include an
> event-loop.h (or some such) and use it.  I'm developing the feeling
> that this is another instance where IWBN if gdb and gdbserver could
> share code.

Yes, of course I agree.

> 2010-05-03  Doug Evans  <dje@google.com>
> 
>         * event-loop.c (struct callback_event): New struct.
...

This is okay too.  Thank you for fixing this.

> +/* If there is still data in the buffer, queue another event to process it,
> +   we can't sleep in select yet.
> +   If there is no data left in the buffer, delete any pending callback.  */

This last sentence appears stale.

> +static void
> +reschedule (void)
> +{
> +  if (readchar_bufcnt > 0 && readchar_callback == NOT_SCHEDULED)
> +    {
> +      readchar_callback = append_callback_event (process_remaining, NULL);
> +    }
>  }

-- 
Pedro Alves


      reply	other threads:[~2010-05-03 20:41 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-30 17:17 Doug Evans
2010-04-30 17:55 ` Pedro Alves
2010-05-03 19:53   ` Doug Evans
2010-05-03 20:41     ` Pedro Alves [this message]

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=201005032141.36926.pedro@codesourcery.com \
    --to=pedro@codesourcery.com \
    --cc=dje@google.com \
    --cc=gdb-patches@sourceware.org \
    /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