I think we have enough information to land a fix for this. I've already reproduced on armhf on xenial with the exact same error:
root@ltrace:~# ltrace ls __libc_start_main(0x12041, 1, 0x7ecd3894, 0x1e795PTRACE_SINGLESTEP: Input/output error 3872 couldn't continue when handling __libc_start_main (0x11d90) at 0x11d90
^C ^\Quit root@ltrace:~# ltrace ps __libc_start_main(0x11cbd, 1, 0x7ee16894, 0x19d01PTRACE_SINGLESTEP: Input/output error 3874 couldn't continue when handling __libc_start_main (0x11694) at 0x11694 ^C^\Quit
And I've done some backporting of ltrace commits already. We'd just need to pinpoint which set of commits are still needed to fix that PTRACE_SINGLESTEP call on ARM. I'll track it down soonish.
I think we have enough information to land a fix for this. I've already reproduced on armhf on xenial with the exact same error:
root@ltrace:~# ltrace ls start_main( 0x12041, 1, 0x7ecd3894, 0x1e795PTRACE_ SINGLESTEP: Input/output error
__libc_
3872 couldn't continue when handling __libc_start_main (0x11d90) at 0x11d90
^C start_main( 0x11cbd, 1, 0x7ee16894, 0x19d01PTRACE_ SINGLESTEP: Input/output error
^\Quit
root@ltrace:~# ltrace ps
__libc_
3874 couldn't continue when handling __libc_start_main (0x11694) at 0x11694
^C^\Quit
And I've done some backporting of ltrace commits already. We'd just need to pinpoint which set of commits are still needed to fix that PTRACE_SINGLESTEP call on ARM. I'll track it down soonish.