From: Ciro Santilli <ciro.santilli@gmail.com>
To: gdb-patches@sourceware.org
Subject: Testsuite docs: explain ptrace_scope and core_pattern requirements.
Date: Fri, 31 Jul 2015 11:41:00 -0000 [thread overview]
Message-ID: <55BB5EF0.7040106@gmail.com> (raw)
From 526bde3e1716a13406f9343ff6a788da9e553e6d Mon Sep 17 00:00:00 2001
From: Ciro Santilli <ciro.santilli@gmail.com>
Date: Fri, 31 Jul 2015 10:05:53 +0200
Subject: [PATCH] Testsuite docs: explain ptrace_scope and core_pattern
requirements.
ptrace_scope can break all attach related tests.
core_pattern can break bigcore.exp.
2015-07-31 Ciro Santilli <ciro.santilli@gmail.com>
gdb:
PR testsuite/18067
PR testsuite/18704
* README (GDB Testsuite): Explain ptrace_scope and core_pattern.
Make section more succinct.
Remove broken Red Hat DejaGNU FTP link.
---
gdb/README | 35 ++++++++++++++++++++++++++---------
1 file changed, 26 insertions(+), 9 deletions(-)
diff --git a/gdb/README b/gdb/README
index d485536..87a4a5f 100644
--- a/gdb/README
+++ b/gdb/README
@@ -595,15 +595,32 @@ think you will be ready to submit the patches.
GDB Testsuite
=============
- Included with the GDB distribution is a DejaGNU based testsuite
-that can either be used to test your newly built GDB, or for
-regression testing a GDB with local modifications.
-
- Running the testsuite requires the prior installation of DejaGNU,
-which is generally available via ftp. The directory
-ftp://sources.redhat.com/pub/dejagnu/ will contain a recent snapshot.
-Once DejaGNU is installed, you can run the tests in one of the
-following ways:
+Requirements:
+
+* DejaGNU
+
+* Ability to attach to processes with the same UID.
+
+ In Linux, you need either to ensure that ptrace is allowed with:
+
+ echo 0 | sudo tee /proc/sys/kernel/yama/ptrace_scope
+
+ or sudo, which is a bad idea.
+
+* Ability to generate big sparse core files.
+
+ In Linux, this is done by default, but it may be broken if your
+ distribution sets:
+
+ /proc/sys/kernel/core_pattern
+
+ to something starting with `|` to use a custom handler program.
+
+ You can fix that with:
+
+ echo | sudo tee /proc/sys/kernel/core_pattern
+
+Usage:
(1) cd gdb-VERSION
make check-gdb
--
1.9.1
next reply other threads:[~2015-07-31 11:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-31 11:41 Ciro Santilli [this message]
2015-07-31 13:35 ` Simon Marchi
2015-07-31 14:03 ` Ciro Santilli
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=55BB5EF0.7040106@gmail.com \
--to=ciro.santilli@gmail.com \
--cc=gdb-patches@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).