From: Jon Ringle <jon@ringle.org>
To: Pedro Alves <palves@redhat.com>
Cc: gdb-patches@sourceware.org, Jon Ringle <jringle@gridpoint.com>
Subject: Re: [PATCH v2] gdbserver: linux_low: elf_64_file_p cache results
Date: Thu, 24 Aug 2017 15:00:00 -0000 [thread overview]
Message-ID: <CAMwGMjx-uSc6y=k-fHw=pTdo5rwMPucRB0KbJrSZjaqhxfuhNQ@mail.gmail.com> (raw)
In-Reply-To: <a275bbe0-cf6c-e9be-e398-7419fd6fc413@redhat.com>
On Thu, Aug 24, 2017 at 10:53 AM, Pedro Alves <palves@redhat.com> wrote:
> On 08/24/2017 03:42 PM, Pedro Alves wrote:
>
>> I'm still mystified about why can't gdbserver read
>> the file after "droproot" has changed user.
>> I assume gdbserver is running as root? Why wouldn't
>> a gdbserver running as root be able to read "jringle"'s
>> /proc file?
>>
>> Does CAP_PTRACE make a difference?
>
> FAOD, I meant CAP_SYS_PTRACE.
Yes, it does make a difference. My testcase works if I add
CAP_SYS_PTRACE to the CapabilityBoundingSet :)
-Jon
prev parent reply other threads:[~2017-08-24 15:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-24 4:45 jon
2017-08-24 9:27 ` Pedro Alves
2017-08-24 14:15 ` Jon Ringle
2017-08-24 14:42 ` Pedro Alves
2017-08-24 14:53 ` Pedro Alves
2017-08-24 15:00 ` Jon Ringle [this message]
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='CAMwGMjx-uSc6y=k-fHw=pTdo5rwMPucRB0KbJrSZjaqhxfuhNQ@mail.gmail.com' \
--to=jon@ringle.org \
--cc=gdb-patches@sourceware.org \
--cc=jringle@gridpoint.com \
--cc=palves@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