From: Pedro Alves <pedro@codesourcery.com>
To: "karthikeyan.s" <informkarthik@gmail.com>
Cc: gdb@sourceware.org
Subject: Re: gdbserver delayed packet event issue
Date: Thu, 11 Nov 2010 12:16:00 -0000 [thread overview]
Message-ID: <201011111216.00997.pedro@codesourcery.com> (raw)
In-Reply-To: <AANLkTimW6tbLdmoSPJp98q88mEVmwvZW_Py=KKaypvsL@mail.gmail.com>
On Thursday 11 November 2010 11:58:08, karthikeyan.s wrote:
> Will try 7.2 but in the meantime, The complete version is 7.1.50.20100416.
I think these were the patches that fixed the issue:
2010-05-03 Doug Evans <>
* event-loop.c (struct callback_event): New struct.
(callback_list): New global.
2010-04-26 Doug Evans <>
* server.c (handle_general_set): Make static.
* remote-utils.c (putpkt_binary_1): Call readchar instead of read.
Print received char after testing for error/eof instead of before.
(input_interrupt): Tweak comment.
So they postdate your snapshot.
--
Pedro Alves
next prev parent reply other threads:[~2010-11-11 12:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-11 5:52 karthikeyan.s
2010-11-11 11:00 ` Pedro Alves
2010-11-11 11:58 ` karthikeyan.s
2010-11-11 12:16 ` Pedro Alves [this message]
2010-11-15 9:29 ` karthikeyan.s
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=201011111216.00997.pedro@codesourcery.com \
--to=pedro@codesourcery.com \
--cc=gdb@sourceware.org \
--cc=informkarthik@gmail.com \
/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