[Bug 1547152] Re: ltrace is throwing segfault while running any of the userspace command

[Steve Langasek]

Thierry, how is this a procps issue?  Praveen reported that 'ltrace ls'
also segfaults, and ls is not part of procps.  This looks more like a
duplicate of bug #1398143 (which has been stalled because there has been
no new upstream release of ltrace, leaving it unclear that picking any
particular upstream commit will give us something that will work on all
architectures).

If there are issues with procps 3.3.10 that warrant an upgrade to
3.3.11, could you please describe what those are?

** Package changed: ubuntu => procps (Ubuntu)

** Changed in: procps (Ubuntu)
       Status: New => Incomplete

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

Title:
  ltrace is throwing segfault while running any of the userspace command

Status in procps package in Ubuntu:
  Incomplete

Bug description:
  == Comment: #0 - Praveen K. Pandey <Praveen.Pandey at in.ibm.com> - 2016-01-25 01:18:25 ==
  Hi ,

     I Installed Ubuntu16.04 In PowerNV and try to run ltrace ls or
  ltrace ps it will fail with segfault .

  
  Reproducible Step :

  1- Install Ubuntu16.04 in PowerNV or as KVM or as PowerVM
  2- Install ltrace  package
  3- Try to run ltrace with any userspace utility like "ltrace ps"

  Actual Result :

  Throw Seg fault

  Expected :

  LOG

  root at lep8d:~# uname -a
  Linux lep8d 4.3.0-7-generic #18-Ubuntu SMP Tue Jan 19 15:47:35 UTC 2016 ppc64le ppc64le ppc64le GNU/Linux
  root at lep8d:~#

  
  root at lep8d:~# ltrace ps
  __printf_chk(1, 0x3fffe4d40028, 0x3fffe4d40038, 0x3fffe4d400e0 <unfinished ...>
  qsort(0x10017850, 0, 0, 0x3fffe4d400e0)                                                                      = <void>
  __gmon_start__(0x3fffe4d4f8df, 47, 0, 0x3fff81c51d68)                                                        = 0
  ferror(0x6)                                                                                                  = 230428656
  __libc_start_main(0x10017e10, 0x10017df8, 0x3fff81d68f48, 0x3fff81d68f38)                                    = 0x3fff81c1ccb0
  readproctab3(0x10017e10, 24, 0x7000000000000000, 0x6c00000000000000)                                         = 0x1000dbc1040
  uptime(0x3fffe4d3faf0, 0, 152, 103)                                                                          = 0x3fffe4d3faf0
  __fpending(0x3fffe4d3faf8, 0, 152, 103)                                                                      = 0
  strrchr("\037 !"#$%&'()*+,-./0123456789:;<=>"..., '\360')                                                    = nil
  escape_command(0x10030f50, 0x3fffe4d3f968, 0, 8)                                                             = 0
  setlocale(LC_NUMERIC, "hijklmnopqrstuvwxyz{|}~\177\200\201\202\203\204\205\206\207"...)                      = nil
  select(1, 0x40087468, 0x3fffe4d3fa00, 0)                                                                     = 1
  __xstat(268534584, "\017", 0x13)                                                                             = 0
  strncmp("", "unknown", 7)                                                                                    = -455870136
  sigfillset(~<1,3,7-8,12,15,18,20,23-24,28,31,36,39,43,47-48,52,55-63>)                                       = 230428768
  getpagesize()                                                                                                = 6
  meminfo(0, 0x100182d0, 0, 0)                                                                                 = 0
  getpagesize( <unfinished ...>
  __stack_chk_fail(0, 0x100182d0, 0, 0 <no return ...>
  --- SIGSEGV (Segmentation fault) ---
  strncpy(0, "Signa", 5)                                                                                       = 0x10017da8
  dlerror()                                                                                                    = "SEGV"
  strcmp("\206 \255\373", "\001\002\003\004\005\006\a\b\t\n\v\f\r\016\017\020\021\022\023\024\025\026\027\030\031\032\033\034\035\036\037 "...Signal 11 (SEGV) caught by ps (procps-ng version 3.3.10).
  ) = 58
  readtask(0, 0, 0x10017de8, 66ps:display.c:66: please report this bug
  )                                                                               = 0
  __snprintf_chk(11, 0, 0x3fff81c5175b, 0)                                                                     = 0x10003e90
  time(0x10003e90)                                                                                             = 30039
  fork()                                                                                                       = 0
  unexpected breakpoint at 0x3fff81b339a4
  --- SIGSEGV (Segmentation fault) ---
  +++ killed by SIGSEGV +++
  root at lep8d:~#

  
  == Comment: #7 - Thierry Fauck <thierry.fauck at fr.ibm.com> - 2016-02-17 14:11:52 ==
  The problem is related to procps-ng 3.3.10
  Upgrade to procps-ng 3.3.11 solves the issue
  Going to Mirror and ask Canonical to advise.

  == Comment: #9 - Thierry Fauck <thierry.fauck at fr.ibm.com> - 2016-02-17 14:13:10 ==
  This bugs is linked to procps-ng 3.3.10 known as having some issues. Is upgrade to 3.3.11 an option ?

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