Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Pedro Alves <palves@redhat.com>
To: Gary Benson <gbenson@redhat.com>, gdb-patches@sourceware.org
Cc: Doug Evans <dje@google.com>, Tom Tromey <tromey@redhat.com>
Subject: Re: [PATCH 2/3 v4] Remove some GDBSERVER checks from linux-ptrace
Date: Thu, 24 Jul 2014 13:25:00 -0000	[thread overview]
Message-ID: <53D108F0.9060100@redhat.com> (raw)
In-Reply-To: <1406206287-6817-3-git-send-email-gbenson@redhat.com>

On 07/24/2014 01:51 PM, Gary Benson wrote:
>  	  /* We got the PID from the grandchild, which means fork
>  	     tracing is supported.  */
> -#ifdef GDBSERVER
> -	  /* Do not enable all the options for now since gdbserver does not
> -	     properly support them.  This restriction will be lifted when
> -	     gdbserver is augmented to support them.  */
> -	  current_ptrace_options |= PTRACE_O_TRACECLONE;
> -#else
> -	  current_ptrace_options |= PTRACE_O_TRACEFORK | PTRACE_O_TRACEVFORK
> -	    | PTRACE_O_TRACECLONE | PTRACE_O_TRACEEXEC;
> -
> -	  /* Do not enable PTRACE_O_TRACEEXIT until GDB is more prepared to
> -	     support read-only process state.  */
> -#endif
> +	  current_ptrace_options |= PTRACE_O_TRACECLONE |
> +	    (additional_flags & ~(PTRACE_O_TRACESYSGOOD
> +				  | PTRACE_O_TRACEVFORKDONE));

This isn't right.  That enables e.g., PTRACE_O_TRACEEXIT, for example,
and possibly invalid flags even.

Please reverse that and spell out the flags we want here explicitly, like:

	  current_ptrace_options |= PTRACE_O_TRACECLONE;
	  current_ptrace_options |= (additional_flags & (PTRACE_O_TRACEFORK
                                 			 | PTRACE_O_TRACEVFORK
		                                         | PTRACE_O_TRACEEXEC));

Thanks,
Pedro Alves


  reply	other threads:[~2014-07-24 13:24 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-24 12:51 [PATCH 0/3 v4] Common code cleanups (part 1) Gary Benson
2014-07-24 12:51 ` [PATCH 2/3 v4] Remove some GDBSERVER checks from linux-ptrace Gary Benson
2014-07-24 13:25   ` Pedro Alves [this message]
2014-07-24 14:09     ` Tom Tromey
2014-07-24 14:17       ` Pedro Alves
2014-07-24 14:13     ` [PATCH 2/3 v5] " Gary Benson
2014-07-24 14:25       ` Pedro Alves
2014-07-24 15:05         ` Gary Benson
2014-07-24 12:51 ` [PATCH 1/3 v4] Introduce common/errors.h Gary Benson
2014-07-24 13:24   ` Pedro Alves
2014-07-24 18:03     ` Doug Evans
2014-07-25  8:51       ` Gary Benson
2014-07-25 10:32         ` Pedro Alves
2014-07-25 11:38           ` Gary Benson
2014-07-25 12:13             ` Pedro Alves
2014-07-25 13:34               ` Gary Benson
2014-07-29 16:44               ` Doug Evans
2014-07-29 17:45                 ` Pedro Alves
2014-07-30  9:43                   ` Gary Benson
2014-07-25 10:19       ` Pedro Alves
2014-07-24 17:52   ` Doug Evans
2014-07-24 22:39     ` Doug Evans
2014-07-25  9:34     ` Gary Benson
2014-07-28 20:16       ` Doug Evans
2014-07-24 13:08 ` [PATCH 3/3 v4] Make gdbserver CORE_ADDR unsigned Gary Benson
2014-07-24 13:36   ` Pedro Alves
2014-07-24 14:07     ` Gary Benson

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=53D108F0.9060100@redhat.com \
    --to=palves@redhat.com \
    --cc=dje@google.com \
    --cc=gbenson@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --cc=tromey@redhat.com \
    /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