This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [PATCH] dynamic printf
- From: Joel Brobecker <brobecker at adacore dot com>
- To: Stan Shebs <stanshebs at earthlink dot net>
- Cc: gdb-patches at sourceware dot org
- Date: Tue, 13 Mar 2012 16:39:39 -0700
- Subject: Re: [PATCH] dynamic printf
- References: <4F4DCDD5.2040807@earthlink.net> <20120229161337.GD3118@adacore.com> <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