From: Michael Snyder <msnyder@vmware.com>
To: Pedro Alves <pedro@codesourcery.com>
Cc: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>,
Stan Shebs <stan@codesourcery.com>
Subject: Re: [RFA] gdb.trace/*.exp send_gdb vs. gdb_test
Date: Fri, 28 May 2010 00:18:00 -0000 [thread overview]
Message-ID: <4BFEFF4B.3010906@vmware.com> (raw)
In-Reply-To: <201005280015.41580.pedro@codesourcery.com>
Pedro Alves wrote:
> ... the test is using an undocumented packet to set
> artificial limits on the remote tracing engine. GDBserver doesn't
> implement that packet. I had never heard of this packet, and I'm
> not sure it makes much sense to have this test nowadays. Can we
> just get rid of the whole test file?
OK with me, but probably not my decision...
next prev parent reply other threads:[~2010-05-27 23:25 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-27 18:22 Michael Snyder
2010-05-27 18:44 ` Pedro Alves
2010-05-27 19:14 ` Michael Snyder
2010-05-27 23:15 ` Pedro Alves
2010-05-27 23:25 ` Pedro Alves
2010-05-28 0:18 ` Michael Snyder [this message]
2010-05-29 0:41 ` Pedro Alves
2010-06-02 19:42 ` Michael Snyder
2010-06-02 21:58 ` Pedro Alves
2010-06-02 22:08 ` Joel Brobecker
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=4BFEFF4B.3010906@vmware.com \
--to=msnyder@vmware.com \
--cc=gdb-patches@sourceware.org \
--cc=pedro@codesourcery.com \
--cc=stan@codesourcery.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