From: Michael Snyder <msnyder@vmware.com>
To: Stan Shebs <stan@codesourcery.com>
Cc: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: [PATCH] One more for MI trace status
Date: Sat, 10 Apr 2010 00:11:00 -0000 [thread overview]
Message-ID: <4BBFC20F.8040802@vmware.com> (raw)
In-Reply-To: <4BBF9429.4090804@codesourcery.com>
Stan Shebs wrote:
> There is one more field that's been overlooked for trace_status_mi -
> total frames created. (More trace status additions are coming, perhaps
> we should revisit the idea of sharing CLI and MI versions...)
>
> I note that MI commands for tracing need testsuite. But there's a
> conundrum; should tests go in gdb.mi or gdb.trace? :-)
I would say in gdb.mi. Just as tests for MI- reverse debugging
should go in mi rather than in gdb.reverse.
next prev parent reply other threads:[~2010-04-10 0:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-09 20:55 Stan Shebs
2010-04-10 0:11 ` Michael Snyder [this message]
2010-04-10 6:56 ` Eli Zaretskii
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=4BBFC20F.8040802@vmware.com \
--to=msnyder@vmware.com \
--cc=gdb-patches@sourceware.org \
--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