public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: Yao Qi <yao@codesourcery.com>
To: Hui Zhu <hui_zhu@mentor.com>
Cc: "gdb@sourceware.org" <gdb@sourceware.org>
Subject: Re: What about add new commands "maintenance agent-breakpoint id expression" and "maintenance agent-eval-breakpoint id expression"
Date: Tue, 12 Jun 2012 02:03:00 -0000	[thread overview]
Message-ID: <4FD6A346.4010108@codesourcery.com> (raw)
In-Reply-To: <4FD68A1A.2040600@mentor.com>

On 06/12/2012 08:15 AM, Hui Zhu wrote:
> Hi guys,
> 
> The "maintenance agent" and "maintenance agent-eval" are for translate
> an expression into remote agent bytecode.
> Both of them got address info from frame.  But when we use tracepoint or
> breakpoint with agent code, this address is from tracepoint or breakpoint.

Agent expression evaluation makes sense in the context of "current
scope" or "current frame".  We can't switch to a frame at any arbitrary
address, because the frame maybe does not exist.

Any examples that "maint agent" doesn't meet your needs in
breakpoint/tracepoint?  It works in the following simple case,

(gdb) b main if (unsigned int) main > 1
(gdb) maintenance agent-eval (unsigned int) main > 1
  0  const64 134513662
  9  zero_ext 32
 11  const8 1
 13  zero_ext 32
 15  swap
 16  less_unsigned
 17  end

-- 
Yao (齐尧)


  reply	other threads:[~2012-06-12  2:03 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-12  0:15 Hui Zhu
2012-06-12  2:03 ` Yao Qi [this message]
2012-06-12 11:42   ` Hui Zhu
2012-06-12 13:15     ` Yao Qi
2012-06-12 23:36 ` Stan Shebs
2012-06-20 10:08   ` Hui Zhu

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=4FD6A346.4010108@codesourcery.com \
    --to=yao@codesourcery.com \
    --cc=gdb@sourceware.org \
    --cc=hui_zhu@mentor.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).