This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [PATCH] MI: new timing command
- From: Nick Roberts <nickrob at snap dot net dot nz>
- To: Eli Zaretskii <eliz at gnu dot org>
- Cc: Vladimir Prus <ghost at cs dot msu dot su>, mark dot kettenis at xs4all dot nl, gdb-patches at sources dot redhat dot com
- Date: Mon, 1 Jan 2007 17:22:18 +1300
- Subject: Re: [PATCH] MI: new timing command
- References: <17814.10139.269708.848818@kahikatea.snap.net.nz> <E1H12lf-0002Zf-GT@zigzag.lvk.cs.msu.su> <200612311609.kBVG9Fgh022431@brahms.sibelius.xs4all.nl> <200612311920.48710.ghost@cs.msu.su> <utzzbafcg.fsf@gnu.org>
> > And lose user/system/elapse time distinction?
>
> You don't have to lose it. How about if we use getrusage directly if
> it's available, else the libiberty replacement? That way, everybody
> will be as happy as they can expect, I think.
If we adopt this approach can you please explain to me how to interpret the
output of get_run_time when getrusage is not availble so I can add it to the
doc.
> > For me, having all those times
> > on Linux is more valuable than having any time at all on Windows.
>
> You are not the only user of GDB.
-enable-timing would only be used by developers of frontends to GDB using MI.
Currently Vladimir and myself do almost appear to be the only users.
> There's no reason to gratuitously
> confine features to the only platform that you are interested in.
It not gratuitous because generalising it involves extra work in areas
we don't understand.
--
Nick http://www.inet.net.nz/~nickrob