From: Tom Tromey <tromey@redhat.com>
To: Pedro Alves <palves@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] fix record "run" regression
Date: Fri, 11 Jul 2014 18:05:00 -0000 [thread overview]
Message-ID: <871ttr7qn7.fsf@fleche.redhat.com> (raw)
In-Reply-To: <53BBB93B.9060207@redhat.com> (Pedro Alves's message of "Tue, 08 Jul 2014 10:26:19 +0100")
>>>>> "Pedro" == Pedro Alves <palves@redhat.com> writes:
Pedro> The comment is stale now. If we can indeed use gdb_run_cmd,
Pedro> then I don't think we need the $use_gdb_stub check?
The use_gdb_stub check is there so that we skip the test on target
remote, which I think shouldn't be expected to work, as you can't re-run
there. But I think I must be missing something.
Tom
next prev parent reply other threads:[~2014-07-11 17:27 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-01 21:45 Tom Tromey
2014-07-02 9:52 ` Pedro Alves
2014-07-03 18:13 ` Tom Tromey
2014-07-04 14:41 ` Pedro Alves
2014-07-07 15:30 ` Tom Tromey
2014-07-08 9:26 ` Pedro Alves
2014-07-11 18:05 ` Tom Tromey [this message]
2014-07-11 18:10 ` Pedro Alves
2014-07-11 18:12 ` Tom Tromey
2014-07-11 18:29 ` Pedro Alves
2014-07-11 21:25 ` Tom Tromey
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=871ttr7qn7.fsf@fleche.redhat.com \
--to=tromey@redhat.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