public inbox for igt-dev@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Ville Syrjala <ville.syrjala@linux.intel.com>
To: igt-dev@lists.freedesktop.org
Subject: [igt-dev] [PATCH i-g-t] lib/igt_core: Detect gdb harder
Date: Wed, 22 Jan 2020 18:43:32 +0200	[thread overview]
Message-ID: <20200122164332.11460-1-ville.syrjala@linux.intel.com> (raw)

From: Ville Syrjälä <ville.syrjala@linux.intel.com>

The current gdb detection only works for the parent igt process,
but none of its children will see the gdb and so won't trap properly
in igt_fail_assert(). Also we will not detect gdb if it was attached
after the fact. Fix all of that by looking for the "TracerPid"
information in /proc/<pid>/status. We'll leave the current "assume
parent may be gdb" approach as a fallback.

Also annoyingly by default gdb will only track a single process.
To make it track all of them, and let them all run simultanously
one needs the following incantations:
 set detach-on-fork off
 set schedule-multiple on

Maybe that will save someone from having to trawl as many
docs/gogole hits as I did.

Signed-off-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
---
 lib/igt_core.c | 38 ++++++++++++++++++++++++++++++++++++--
 1 file changed, 36 insertions(+), 2 deletions(-)

diff --git a/lib/igt_core.c b/lib/igt_core.c
index 0a0068946a6a..109b5926eac4 100644
--- a/lib/igt_core.c
+++ b/lib/igt_core.c
@@ -1609,12 +1609,12 @@ void igt_describe_f(const char *fmt, ...)
 	assert(ret < sizeof(__current_description));
 }
 
-static bool running_under_gdb(void)
+static bool is_gdb(pid_t pid)
 {
 	char pathname[30], buf[1024];
 	ssize_t len;
 
-	sprintf(pathname, "/proc/%d/exe", getppid());
+	sprintf(pathname, "/proc/%d/exe", pid);
 	len = readlink(pathname, buf, sizeof(buf) - 1);
 	if (len < 0)
 		return false;
@@ -1624,6 +1624,40 @@ static bool running_under_gdb(void)
 	return strncmp(basename(buf), "gdb", 3) == 0;
 }
 
+static pid_t tracer_pid(void)
+{
+	char pathname[30];
+	pid_t pid = 0;
+	FILE *f;
+
+	sprintf(pathname, "/proc/%d/status", getpid());
+
+	f = fopen(pathname, "r");
+	if (!f)
+		return getppid();
+
+	for (;;) {
+		char buf[1024];
+		char *s;
+
+		s = fgets(buf, sizeof(buf), f);
+		if (!s)
+			break;
+
+		if (sscanf(s, "TracerPid: %d", &pid) == 1)
+			break;
+	}
+
+	fclose(f);
+
+	return pid ?: getppid();
+}
+
+static bool running_under_gdb(void)
+{
+	return is_gdb(tracer_pid());
+}
+
 static void __write_stderr(const char *str, size_t len)
 {
 	igt_ignore_warn(write(STDERR_FILENO, str, len));
-- 
2.24.1

_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev

             reply	other threads:[~2020-01-22 16:43 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-22 16:43 Ville Syrjala [this message]
2020-01-22 17:09 ` [igt-dev] [PATCH i-g-t] lib/igt_core: Detect gdb harder Chris Wilson
2020-01-22 17:21   ` Ville Syrjälä
2020-01-22 17:31     ` Chris Wilson
2020-01-22 19:56 ` [igt-dev] ✓ Fi.CI.BAT: success for " Patchwork
2020-01-23 13:51 ` [igt-dev] ✗ GitLab.Pipeline: warning " Patchwork
2020-01-23 22:59 ` [igt-dev] ✓ Fi.CI.IGT: success " Patchwork

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=20200122164332.11460-1-ville.syrjala@linux.intel.com \
    --to=ville.syrjala@linux.intel.com \
    --cc=igt-dev@lists.freedesktop.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