From cbae097bbdef50171500394bbb406e8b73db35b5 Mon Sep 17 00:00:00 2001 From: Daniel Jacobowitz Date: Sat, 20 Jan 2007 18:33:27 +0000 Subject: [PATCH] * gdb.base/bigcore.c (RLIMIT_CAP): Define. (maximize_rlimit): Reduce limits on 64-bit systems. --- gdb/testsuite/ChangeLog | 5 +++++ gdb/testsuite/gdb.base/bigcore.c | 9 +++++++++ 2 files changed, 14 insertions(+) diff --git a/gdb/testsuite/ChangeLog b/gdb/testsuite/ChangeLog index 81cbce0522..c876e51032 100644 --- a/gdb/testsuite/ChangeLog +++ b/gdb/testsuite/ChangeLog @@ -1,3 +1,8 @@ +2007-01-20 Daniel Jacobowitz + + * gdb.base/bigcore.c (RLIMIT_CAP): Define. + (maximize_rlimit): Reduce limits on 64-bit systems. + 2007-01-19 Mark Kettenis From Marcus Deuling : diff --git a/gdb/testsuite/gdb.base/bigcore.c b/gdb/testsuite/gdb.base/bigcore.c index 46b5e2afbf..367485b568 100644 --- a/gdb/testsuite/gdb.base/bigcore.c +++ b/gdb/testsuite/gdb.base/bigcore.c @@ -31,6 +31,13 @@ #include #include +/* This test was written for >2GB core files on 32-bit systems. On + current 64-bit systems, generating a >4EB (2 ** 63) core file is + not practical, and getting as close as we can takes a lot of + useless CPU time. So limit ourselves to a bit bigger than + 32-bit, which is still a useful test. */ +#define RLIMIT_CAP (1ULL << 34) + /* Print routines: The following are so that printf et.al. can be avoided. Those @@ -110,6 +117,8 @@ maximize_rlimit (int resource, const char *prefix) print_rlimit (resource); getrlimit (resource, &rl); rl.rlim_cur = rl.rlim_max; + if (sizeof (rl.rlim_cur) >= sizeof (RLIMIT_CAP)) + rl.rlim_cur = (rlim_t) RLIMIT_CAP; setrlimit (resource, &rl); print_string (" -> "); print_rlimit (resource); -- 2.11.0