Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Pedro Alves <palves@redhat.com>
To: Daniel Colascione <dancol@dancol.org>, gdb-patches@sourceware.org
Subject: Re: [PATCH] Warn users about mismatched PID namespaces
Date: Fri, 07 Nov 2014 12:49:00 -0000	[thread overview]
Message-ID: <545CBFEB.7000907@redhat.com> (raw)
In-Reply-To: <5451AB7E.40709@dancol.org>

On 10/30/2014 03:07 AM, Daniel Colascione wrote:

> diff --git a/gdb/linux-thread-db.c b/gdb/linux-thread-db.c
> index 352fac1..4089417 100644
> - --- a/gdb/linux-thread-db.c
> +++ b/gdb/linux-thread-db.c
> @@ -1223,6 +1223,25 @@ thread_db_new_objfile (struct objfile *objfile)
>  static void
>  thread_db_inferior_created (struct target_ops *target, int from_tty)
>  {

This hook is called even if the current target isn't a native process.
E.g., you may have loaded a core, in which case looking at
getpid or /proc doesn't make sense.  Or you may be debugging with
"target sim", or a remote process with gdbserver [1], etc.

We need this same check that thread_db_load does:

  /* Don't attempt to use thread_db for remote targets.  */
  if (!(target_can_run (&current_target) || core_bfd))
    return 0;

[1] BTW, could I interest in giving gdbserver/thread-db.c the
    same treatment?

> +  /* If the child is in a different PID namespace, its idea of its PID
> +     will differ from our idea of its PID.  When we scan the child's
> +     thread list, we'll mistakenly think it has no threads since the
> +     thread PID fields won't match the PID we give to
> +     libthread_db.  */
> +  char *our_pid_ns = linux_proc_pid_get_ns (getpid (), "pid");
> +  char *inferior_pid_ns = linux_proc_pid_get_ns (
> +    ptid_get_pid (inferior_ptid), "pid");
> +
> +  if (our_pid_ns != NULL && inferior_pid_ns != NULL &&

Put '&&' at the beginning of the next line.

> +      strcmp (our_pid_ns, inferior_pid_ns) != 0)


> +    {
> +      warning (_ ("Target and debugger are in different PID namespaces; "
> +		  "thread lists and other data are likely unreliable"));
> +    }
> +
> +  xfree (our_pid_ns);
> +  xfree (inferior_pid_ns);

Please factor this new code to a function; Having it in a function
makes it easier to move the caller around if necessary.

> +
>    check_for_thread_db ();
>  }
> 
> diff --git a/gdb/nat/linux-procfs.c b/gdb/nat/linux-procfs.c
> index 30797da..8efccba 100644
> - --- a/gdb/nat/linux-procfs.c
> +++ b/gdb/nat/linux-procfs.c
> @@ -113,3 +113,22 @@ linux_proc_pid_is_zombie (pid_t pid)
>  {
>    return linux_proc_pid_has_state (pid, "Z (zombie)");
>  }
> +
> +/* See linux-procfs.h declaration.  */
> +
> +char*
> +linux_proc_pid_get_ns (pid_t pid, const char *ns)
> +{
> +  char buf[100];
> +  char nsval[64];
> +  int ret;
> +  snprintf (buf, sizeof (buf), "/proc/%d/ns/%s", (int) pid, ns);

Use xsnprintf .

> 
> +/* Return an opaque string identifying PID's NS namespace or NULL if
> + * the information is unavailable.  The returned string must be
> + * released with xfree.  */
> +
> +extern char* linux_proc_pid_get_ns (pid_t pid, const char *ns);

Space between char and *.

Thanks,
Pedro Alves


  parent reply	other threads:[~2014-11-07 12:49 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-30  3:09 Daniel Colascione
2014-10-30 12:23 ` Pedro Alves
2014-10-30 12:32   ` Daniel Colascione
2014-10-30 12:49     ` Pedro Alves
2014-10-30 12:51       ` Daniel Colascione
2014-10-30 13:12         ` Pedro Alves
2014-10-30 13:13           ` Pedro Alves
2014-10-30 15:41           ` Daniel Colascione
2014-10-30 16:18             ` Pedro Alves
2014-11-05 10:55           ` Pedro Alves
2014-11-06 21:12             ` Daniel Colascione
2014-11-07 12:50               ` Pedro Alves
2014-11-07 12:49 ` Pedro Alves [this message]
2014-11-09 21:23   ` Daniel Colascione
2014-11-11 14:25     ` Pedro Alves

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=545CBFEB.7000907@redhat.com \
    --to=palves@redhat.com \
    --cc=dancol@dancol.org \
    --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