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: Daniel Jacobowitz <drow at false dot org>
To: Eli Zaretskii <eliz at gnu dot org>
Cc: Nick Roberts <nickrob at snap dot net dot nz>, gdb-patches at sourceware dot org
Date: Sat, 30 Dec 2006 23:25:47 -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>

On Sun, Dec 31, 2006 at 06:21:59AM +0200, Eli Zaretskii wrote:
> > Is there any way of finding out e.g online database?
> 
> Sorry, I don't know.  Anyone?

The autoconf manual has information about this sort of thing.  I see
that libiberty guards it, sometimes with HAVE_GETRUSAGE and other times
with that and HAVE_SYS_RESOURCE_H.

Will libiberty's get_run_time suffice for whatever you were doing,
Nick?

-- 
Daniel Jacobowitz
CodeSourcery

Follow-Ups:
- Re: [PATCH] MI: new timing command
  - From: Nick Roberts

References:
- [PATCH] MI: new timing command
  - From: Nick Roberts
- Re: [PATCH] MI: new timing command
  - From: Eli Zaretskii
- Re: [PATCH] MI: new timing command
  - From: Nick Roberts
- Re: [PATCH] MI: new timing command
  - From: Eli Zaretskii

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