Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Stan Shebs <stan@codesourcery.com>
To: Vladimir Prus <vladimir@codesourcery.com>
Cc: Stan Shebs <stan@codesourcery.com>, gdb-patches@sourceware.org
Subject: Re: [MI tracepoints 2/9] unify breakpoint commands and tracepoint  actions
Date: Mon, 22 Mar 2010 15:01:00 -0000	[thread overview]
Message-ID: <4BA78648.6090202@codesourcery.com> (raw)
In-Reply-To: <201003161438.27874.vladimir@codesourcery.com>

Vladimir Prus wrote:
> Here's a revised version, also addressing Pedro's comments.
>   
Looks great, just one little thing left to fix:

+      if (strstr (c->line, "eval ") == c->line)
+	error (_("The 'eval' command can only be used for tracepoints"));


The command is now "teval" instead of "eval".

With that change, we should be ready to roll in all 9 patches.  Thanks 
again!

Stan





  reply	other threads:[~2010-03-22 15:01 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-14  8:47 Vladimir Prus
2010-03-15 17:48 ` Stan Shebs
2010-03-15 21:00   ` Tom Tromey
2010-03-16 11:38   ` Vladimir Prus
2010-03-22 15:01     ` Stan Shebs [this message]
2010-03-23 21:37       ` Vladimir Prus
2010-03-16  0:56 ` 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=4BA78648.6090202@codesourcery.com \
    --to=stan@codesourcery.com \
    --cc=gdb-patches@sourceware.org \
    --cc=vladimir@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