From: Yao Qi <qiyaoltc@gmail.com>
To: Pedro Alves <palves@redhat.com>
Cc: Yao Qi <qiyaoltc@gmail.com>, gdb-patches@sourceware.org
Subject: Re: [PATCH] Fix fail in gdb.base/interrupt-noterm.exp
Date: Fri, 22 Jan 2016 17:14:00 -0000 [thread overview]
Message-ID: <86twm5r0yp.fsf@gmail.com> (raw)
In-Reply-To: <56A25D13.2080608@redhat.com> (Pedro Alves's message of "Fri, 22 Jan 2016 16:47:15 +0000")
Pedro Alves <palves@redhat.com> writes:
> Can you expand the rationale some more?
>
> E.g., why is this not a gdbserver bug? Instintively I'd say it is.
The interaction between GDB and GDBserver is like this,
1. GDB sends vCont;c and doesn't wait for the stop reply because
"continue &" is background command,
2. GDBserver receives vCont;c, enables the async i/o (by
enable_async_io) and resumes the inferior.
3. GDB sends interrupt packet,
#1 happens before #2 and #3, but the order of #2 and #3 is not
determined. If #2 happens before #3, it is fine, otherwise, the
GDBserver doesn't know the interrupt from GDB.
--
Yao (齐尧)
next prev parent reply other threads:[~2016-01-22 17:14 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-22 16:29 Yao Qi
2016-01-22 16:47 ` Pedro Alves
2016-01-22 17:14 ` Yao Qi [this message]
2016-01-22 17:35 ` Pedro Alves
2016-01-22 18:30 ` Pedro Alves
2016-01-25 9:30 ` Yao Qi
2016-01-25 10:43 ` Pedro Alves
2016-01-26 9:59 ` [PATCH 0/2 V2] Fix a " Yao Qi
2016-01-26 9:59 ` [PATCH 1/2] [GDBserver] Check input interrupt after reading in a packet Yao Qi
2016-01-26 11:42 ` Pedro Alves
2016-01-26 13:53 ` Yao Qi
2016-01-26 9:59 ` [PATCH 2/2] [GDBserver] Block and unblock SIGIO Yao Qi
2016-01-26 12:01 ` Pedro Alves
2016-01-26 13:55 ` Yao Qi
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=86twm5r0yp.fsf@gmail.com \
--to=qiyaoltc@gmail.com \
--cc=gdb-patches@sourceware.org \
--cc=palves@redhat.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