This is the mail archive of the gdb-patches@sourceware.org mailing list for the GDB project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: [PATCH] MI: new timing command


> From: Nick Roberts <nickrob@snap.net.nz>
> Date: Mon, 1 Jan 2007 17:05:01 +1300
> Cc: ghost@cs.msu.su, gdb-patches@sources.redhat.com
> 
> I'm not familiar with get_run_time but I'm sure we all know getrusage through
> the time shell command.  If the frontend appears to be slow I can see if that's
> due to MI or other things running on my system.  I'm not sure that I can do
> that with get_run_time.  I would like to start with getrusage and then when
> there are hoards of developers rushing to develop frontends for GDB using
> MI on Windows, I'll be happy to accommodate them.

Once again, this is not about Windows, this is about _any_ platform
that lacks getrusage.

All you need to do is call get_run_time in the #else branch of the
HAVE_GETRUSAGE test, instead of erroring out.  I'm amazed such a
simple solution causes such a prolonged dispute.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]