This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [PATCH 0/4 V3] GDB Performance testing
- From: Doug Evans <dje at google dot com>
- To: Yao Qi <yao at codesourcery dot com>
- Cc: gdb-patches <gdb-patches at sourceware dot org>
- Date: Thu, 24 Oct 2013 19:59:49 -0700
- Subject: Re: [PATCH 0/4 V3] GDB Performance testing
- Authentication-results: sourceware.org; auth=none
- References: <1381907353-30013-1-git-send-email-yao at codesourcery dot com>
On Wed, Oct 16, 2013 at 12:09 AM, Yao Qi <yao@codesourcery.com> wrote:
> Hi,
> Here is the V3 of GDB performance testing. The changes in V3 can be
> found in each patch, and they address all review comments.
Cool.
> $ make check-perf RUNTESTFLAGS="--target_board=native-gdbserver GDB_PERFORMANCE_TIMEOUT=4000 solib.exp"
I haven't read the rest in the series yet, but while it's on my mind I
want to write this down so I don't forget.
Another thing the test harness needs is the ability to set a limit on
the memory size of gdb.
It's a safety net because sometimes changes happen that cause memory
usage to really swell and we don't want to drag a machine into
thrashing just to get through the test.
Using system monitored settings for both cpu and memory usage would be
good (ulimit).