The Debian change was ingested into ltrace (0.7.3-6.1ubuntu1) disco.
Mark the issue as "Fix Released".
** Changed in: ltrace (Ubuntu)
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: ltrace (Debian)
Status: Unknown => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/771805
Title:
[armel/armhf] ltrace hangs
To manage notifications about this bug
** Bug watch added: Debian Bug tracker #898113
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=898113
** Also affects: ltrace (Debian) via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=898113
Importance: Unknown
Status: Unknown
--
You received this bug notification because
Um. I have also been getting sample problem on Ubuntu/ARM 14.04 as
following:
root@target:~# ltrace
ltrace: too few arguments
Try `ltrace --help' for more information.
root@target:~# ltrace ls
__libc_start_main(0x9ee9, 1, 0x7ec70894, 0x156b1PTRACE_SINGLESTEP: Input/output
error
1365 couldn't
I have got the "PTRACE_SINGLESTEP" error message in case that I try to use
ltrace 0.7.3 on Ubuntu/ARM 14.04.
Actually, This issue resulted from the change of the Linux Kernel.
Please, see the
https://code.kodo.org.uk/dom/buildroot/commit/efee851c614926dd9ed0f49c4808a6d9b4f64eb0
--
You
