From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>
Cc: igt-dev@lists.freedesktop.org
Subject: Re: [igt-dev] [PATCH i-g-t] lib/igt_core: Detect gdb harder
Date: Wed, 22 Jan 2020 19:21:26 +0200 [thread overview]
Message-ID: <20200122172126.GD13686@intel.com> (raw)
In-Reply-To: <157971295973.15024.11653081154812513001@skylake-alporthouse-com>
On Wed, Jan 22, 2020 at 05:09:19PM +0000, Chris Wilson wrote:
> Quoting Ville Syrjala (2020-01-22 16:43:32)
> > 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);
>
> I'd prefer fgetline, /proc/<pid>status is >1024 bytes so there's always
> that chance we cut the TracerPid line.
fgets() reads at most one line (which means my 1024 copypasta is
probably a bit much). Not sure what fgetline() is.
>
> > + if (!s)
> > + break;
> > +
> > + if (sscanf(s, "TracerPid: %d", &pid) == 1)
> > + break;
> > + }
> > +
> > + fclose(f);
> > +
> > + return pid ?: getppid();
>
> Makes sense.
>
> > +}
> > +
> > +static bool running_under_gdb(void)
> > +{
>
> /*
> * Annoyingly by default gdb will only track a single process.
> * To make it track all of them, and let them all run simultaneously
> * one needs the following incantations:
> * set detach-on-fork off
> * set schedule-multiple on
> */
Yeah, a comment is probably a good idea for this.
>
>
> TIL two things, so
> Reviewed-by: Chris Wilson <chris@chris-wilson.co.uk>
> -Chris
--
Ville Syrjälä
Intel
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev
next prev parent reply other threads:[~2020-01-22 17:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-22 16:43 [igt-dev] [PATCH i-g-t] lib/igt_core: Detect gdb harder Ville Syrjala
2020-01-22 17:09 ` Chris Wilson
2020-01-22 17:21 ` Ville Syrjälä [this message]
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=20200122172126.GD13686@intel.com \
--to=ville.syrjala@linux.intel.com \
--cc=chris@chris-wilson.co.uk \
--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