[Bug 1317136] Re: useful Yama EPERM error message missing (regression)

[Brian Murray]

Hello Kees, or anyone else affected,

Accepted ltrace into trusty-proposed. The package will build now and be
available at http://launchpad.net/ubuntu/+source/ltrace/0.7.3-4ubuntu5.1
in a few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed.  Your feedback will aid us getting this update
out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, and change the tag
from verification-needed to verification-done. If it does not fix the
bug for you, please add a comment stating that, and change the tag to
verification-failed.  In either case, details of your testing will help
us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

** Changed in: ltrace (Ubuntu Trusty)
       Status: In Progress => Fix Committed

** Tags added: verification-needed

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to gdb in Ubuntu.
https://bugs.launchpad.net/bugs/1317136

Title:
  useful Yama EPERM error message missing (regression)

Status in “gdb” package in Ubuntu:
  Fix Released
Status in “ltrace” package in Ubuntu:
  Fix Released
Status in “gdb” source package in Trusty:
  In Progress
Status in “ltrace” source package in Trusty:
  Fix Committed
Status in “gdb” source package in Utopic:
  Fix Released
Status in “ltrace” source package in Utopic:
  Fix Released

Bug description:
  SRU:

  [Impact]
  ltrace and gdb users may be stumped by the ptrace restrictions that are enabled by default in Ubuntu. Unfortunately, the patches that print a detailed informative error message in previous Ubuntu releases no longer work or haven't been applied in Trusty.

  [Test Case]

  $ ltrace -p 1 should display the following:
  Cannot attach to pid 1: Operation not permitted
  Could not attach to process.  If your uid matches the uid of the target
  process, check the setting of /proc/sys/kernel/yama/ptrace_scope, or try
  again as the root user.  For more details, see /etc/sysctl.d/10-ptrace.conf

  $ gdb -p 1 should display a similar error message

  [Regression Potential]
  This patch is in the error condition, so regression is unlikely. Worst case, it could prevent ltrace or gdb from working at all.


  
  Original description:
  Trusty's gdb and ltrace have lost the helpful error details when ptrace attach fails. Compare to strace:

  $ strace -p 1
  strace: attach: ptrace(PTRACE_ATTACH, ...): Operation not permitted
  Could not attach to process.  If your uid matches the uid of the target
  process, check the setting of /proc/sys/kernel/yama/ptrace_scope, or try
  again as the root user.  For more details, see /etc/sysctl.d/10-ptrace.conf

  $ gdb -p 1
  GNU gdb (Ubuntu 7.7-0ubuntu3) 7.7
  ...
  Attaching to process 1
  ptrace: Operation not permitted.

  $ ltrace -p 1
  Cannot attach to pid 1: Operation not permitted

  In Precise ltrace has the correct error (though gdb is still missing
  it -- this was lost quite some time ago it seems):

  $ ltrace -p 1
  Could not attach to process.  If your uid matches the uid of the target
  process, check the setting of /proc/sys/kernel/yama/ptrace_scope, or try
  again as the root user.  For more details, see /etc/sysctl.d/10-ptrace.conf
  Cannot attach to pid 1: Operation not permitted

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdb/+bug/1317136/+subscriptions