This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [PATCH] MI: new timing command
- From: Daniel Jacobowitz <drow at false dot org>
- To: Nick Roberts <nickrob at snap dot net dot nz>
- Cc: Eli Zaretskii <eliz at gnu dot org>, gdb-patches at sourceware dot org
- Date: Mon, 1 Jan 2007 11:21:43 -0500
- Subject: Re: [PATCH] MI: new timing command
- References: <17814.10139.269708.848818@kahikatea.snap.net.nz> <u8xgp2wnm.fsf@gnu.org> <17814.58031.865155.682869@kahikatea.snap.net.nz> <umz541yqg.fsf@gnu.org> <20061231042547.GA3236@nevyn.them.org> <17815.18190.987950.612053@kahikatea.snap.net.nz> <20061231054946.GA4873@nevyn.them.org> <17815.27092.497145.908734@kahikatea.snap.net.nz> <20061231151527.GC16449@nevyn.them.org> <17816.53619.895367.798678@farnswood.snap.net.nz>
On Mon, Jan 01, 2007 at 10:16:35PM +1300, Nick Roberts wrote:
> I wasn't aware of "maint time 1" which does indeed seem very similar. In that
> case don't understand why you suggested "-gdb-set mi profiling on" and not
> "-gdb-set mi set time on".
Indeed, it was a mistake on my part.
> Anyway, in the case of MI, I'm not sure that you
> would want the user to be able to turn it on, so I'm not sure that the same
> setting is a good idea. Initially I would just use it manually from the
> command line. I don't currently have a front end that can consume the output
> but it clearly makes sense for the future.
It's just a new field in various outputs; shouldn't a properly written
MI parser ignore them? Anyway, it might not be wise to make it easy
for end users to enable it, indeed. That's a good reason to use
-enable-timings as you/Apple did.
--
Daniel Jacobowitz
CodeSourcery