From: Pedro Alves <pedro@codesourcery.com>
To: Stan Shebs <stan@codesourcery.com>
Cc: gdb-patches@sourceware.org
Subject: Re: Switch out and in of tfind mode, when handling an event, in non-stop mode.
Date: Wed, 24 Feb 2010 15:59:00 -0000 [thread overview]
Message-ID: <201002241558.51983.pedro@codesourcery.com> (raw)
In-Reply-To: <4B84D657.2060406@codesourcery.com>
On Wednesday 24 February 2010 07:33:43, Stan Shebs wrote:
> Pedro Alves wrote:
> > [...] Hence, this patch
> > below. I've applied it.
> >
> Thanks! I wonder if it should go into 7.1 too?
It's a pretty safe patch, in terms of likeliness of
causing unexpected troubles. I guess it could go in
7.1, yeah, though I'm not exactly clear on how useable
tracepoints in 7.1 actually are.
> We don't really have a
> specific goal for how well tracepoints should work in the release...
Me neither... I'm assuming that 7.2 will be the release
tracepoints will be actually useable in the field. E.g., 7.1
missed the tracepoints actions + breakpoints commands
merge, and MI tracepoints support. And it won't ship with
a target users can do tracing with either. :-)
--
Pedro Alves
next prev parent reply other threads:[~2010-02-24 15:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-24 1:08 Pedro Alves
2010-02-24 7:33 ` Stan Shebs
2010-02-24 15:59 ` Pedro Alves [this message]
2010-02-24 21:44 ` Pedro Alves
2011-02-11 15:10 ` Pedro Alves
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=201002241558.51983.pedro@codesourcery.com \
--to=pedro@codesourcery.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