From: Tom Tromey <tromey@redhat.com>
To: Jan Kratochvil <jan.kratochvil@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [patchv2 2/2] Fix CTRL-C for remote.c (PR remote/15297)
Date: Thu, 25 Jul 2013 15:29:00 -0000 [thread overview]
Message-ID: <87y58uves3.fsf@fleche.redhat.com> (raw)
In-Reply-To: <20130725152523.GA20909@host2.jankratochvil.net> (Jan Kratochvil's message of "Thu, 25 Jul 2013 17:25:23 +0200")
>>>>> "Jan" == Jan Kratochvil <jan.kratochvil@redhat.com> writes:
>> Can you characterize the failure modes? Or will I see it if I add a
>> target-async+non-stop case to your new .exp?
Jan> ^^^^^^^^^^^^^^^^^^^^^ - this one is there:
Sorry, I meant target-async+full-stop.
Jan> You are right this "async-allstop" case has to be added. I was not
Jan> sure what is the expected behavior/output in such case, maybe GDB
Jan> behaves correctly.
Ok, fair enough. I will look after it goes in.
Tom
prev parent reply other threads:[~2013-07-25 15:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20130630181110.GB29548@host2.jankratochvil.net>
2013-07-25 15:20 ` Tom Tromey
2013-07-25 15:25 ` Jan Kratochvil
2013-07-25 15:29 ` Tom Tromey [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=87y58uves3.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=jan.kratochvil@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