Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Joel Brobecker <brobecker@adacore.com>
To: Stan Shebs <stanshebs@earthlink.net>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] dynamic printf
Date: Tue, 13 Mar 2012 23:40:00 -0000	[thread overview]
Message-ID: <20120313233939.GX2853@adacore.com> (raw)
In-Reply-To: <4F5FD4DD.1010603@earthlink.net>

> >Or like a tracepoint that does printf? Would it influence an operation
> >such as "next", for instance?
> >
> >
> 
> There is a tracepoint similarity; one of the vague future-direction
> ideas is to somehow refactor tracing and breaking so one could shift
> back and forth freely, for instance to decide to collect some data
> at a breakpoint, without having to do the formalized trace
> experiment setup.
> 
> I'm not sure what you mean by influencing "next"?

I was referring to some suggestions that your new feature was equivalent
to a breakpoint with two commands that do the printing followed by a
continue.  This method looks like a great way of tracing code (meaning
adding debugging traces), except that if the breakpoint is hit during
a "next", then you get your trace followed by your program running away
until hitting the next breakpoint, instead of stopping on the next line
of code. That's why I like referring to the tracepoint terminology...

-- 
Joel


  reply	other threads:[~2012-03-13 23:40 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-29  9:14 Stan Shebs
2012-02-29 10:28 ` Andreas Schwab
2012-03-13 23:09   ` Stan Shebs
2012-03-14 14:47     ` Marc Khouzam
2012-03-14 15:28     ` Tom Tromey
2012-02-29 16:16 ` Joel Brobecker
2012-03-13 23:15   ` Stan Shebs
2012-03-13 23:40     ` Joel Brobecker [this message]
2012-02-29 18:21 ` Eli Zaretskii
2012-03-13 23:20   ` Stan Shebs
2012-03-01 14:04 ` Hui Zhu
2012-03-04  6:31   ` Hui Zhu
2012-03-08 21:08 ` Tom Tromey
2012-03-13 23:51   ` Stan Shebs
2012-03-14 15:24     ` Tom Tromey

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=20120313233939.GX2853@adacore.com \
    --to=brobecker@adacore.com \
    --cc=gdb-patches@sourceware.org \
    --cc=stanshebs@earthlink.net \
    /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