From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 12013 invoked by alias); 1 Jan 2007 05:58:04 -0000 Received: (qmail 12005 invoked by uid 22791); 1 Jan 2007 05:58:03 -0000 X-Spam-Check-By: sourceware.org Received: from fencepost.gnu.org (HELO fencepost.gnu.org) (199.232.76.164) by sourceware.org (qpsmtpd/0.31) with ESMTP; Mon, 01 Jan 2007 05:57:59 +0000 Received: from eliz by fencepost.gnu.org with local (Exim 4.60) (envelope-from ) id 1H1GB1-0000Da-7F; Mon, 01 Jan 2007 00:57:39 -0500 From: Eli Zaretskii To: Nick Roberts CC: mark.kettenis@xs4all.nl, ghost@cs.msu.su, gdb-patches@sources.redhat.com In-reply-to: <17816.34925.514170.51734@farnswood.snap.net.nz> (message from Nick Roberts on Mon, 1 Jan 2007 17:05:01 +1300) Subject: Re: [PATCH] MI: new timing command Reply-to: Eli Zaretskii References: <17814.10139.269708.848818@kahikatea.snap.net.nz> <17814.58031.865155.682869@kahikatea.snap.net.nz> <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> <200612311524.kBVFObud010411@brahms.sibelius.xs4all.nl> <200612311609.kBVG9Fgh022431@brahms.sibelius.xs4all.nl> <17816.34925.514170.51734@farnswood.snap.net.nz> Message-Id: Date: Mon, 01 Jan 2007 05:58:00 -0000 X-IsSubscribed: yes Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org X-SW-Source: 2007-01/txt/msg00010.txt.bz2 > From: Nick Roberts > 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.