Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Hui Zhu <teawater@gmail.com>
Cc: gdb-patches@sourceware.org, msnyder@vmware.com, green@moxielogic.com
Subject: Re: [RFA/RFC Prec] Add process record skip 6/6 (doc)
Date: Tue, 01 Sep 2009 17:12:00 -0000	[thread overview]
Message-ID: <8363c2a8we.fsf@gnu.org> (raw)
In-Reply-To: <daef60380909010156y379e470pf9781f18aa198427@mail.gmail.com>

> From: Hui Zhu <teawater@gmail.com>
> Date: Tue, 1 Sep 2009 16:56:42 +0800
> Cc: gdb-patches@sourceware.org, msnyder@vmware.com, green@moxielogic.com
> 
> I think this idea is not bad.  But when user set a simple_function to
> GDB, check if this function is really a simple function or not is not
> easy.

Why should GDB care?  Let the user care.

> What about keep this idea and add special patch for it when gdb
> support record skip?

<Shrug> If no one else is concerned about this, I can live with that.

> +beginning of a function.  When this breaks break, if
                             ^^^^^^^^^^^^^^^^^^^^^^
"When this breakpoint breaks"

Otherwise, fine.


  reply	other threads:[~2009-09-01 17:12 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-19  8:15 Hui Zhu
2009-08-19 18:45 ` Eli Zaretskii
2009-08-23  3:52   ` Hui Zhu
2009-08-23 22:48     ` Eli Zaretskii
2009-08-24  9:53       ` Hui Zhu
2009-08-24 19:14         ` Eli Zaretskii
2009-08-25  4:25           ` Hui Zhu
2009-08-26 17:54             ` Eli Zaretskii
2009-08-31 13:59               ` Hui Zhu
2009-08-31 17:41                 ` Eli Zaretskii
2009-09-01  8:57                   ` Hui Zhu
2009-09-01 17:12                     ` Eli Zaretskii [this message]
2009-09-02 12:01                       ` 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=8363c2a8we.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=gdb-patches@sourceware.org \
    --cc=green@moxielogic.com \
    --cc=msnyder@vmware.com \
    --cc=teawater@gmail.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