[Ltrace-devel] No output on Ubuntu 16.10

[Stefano Cristalli]

Hello,

thank you for your response.
All the useful details I could think of are included in my Stack Overflow post:

kernel 4.8.0-42-generic
ltrace package 0.7.3-5.1ubuntu4 (when installed from package)
gcc 6.2.0

Another person in my lab was able to reproduce the issue by installing
Ubuntu 16.10 in VMWare. "ltrace ls" just doesn't work.
I passed my ls binary to someone else who is running Ubuntu 16.04 (and
doesn't have the problem), and even in his system with his ltrace my
binary doesn't get traced... so it seems it's something related to the
binary.

Meanwhile I checked with the command hardening-check if the binaries
are PIE... turns out they all are (the ones that don't work). So I
guess the user who commented on Stack Overflow got this right and the
problem is "solved", I was mistaken.

What I don't understand now is how you can have this working in a
fresh Ubuntu 16.10 install. May I ask if the binaries in your system
are PIE? What is the hash of your /bin/ls? The MD5 of mine and my
colleague's is 1d1ad8652015e47b8f45f450522c1a8a.

Thanks again.
Best regards.

Stefano Cristalli

2017-04-06 5:35 GMT+02:00 Dima Kogan <dima at secretsauce.net>:
> Stefano Cristalli <stefanocristalli at gmail.com> writes:
>
>> I post to this list with the hope to solve the problem I posted
>> yesterday on Stack Overflow:
>> http://stackoverflow.com/questions/43213505/no-output-when-running-ltrace
>>
>> ltrace (installed either from package or from source) shows no output
>> on both compiled binaries and system binaries (e.g. /bin/ls), while it
>> works with some binaries compiled elsewhere. Since another user
>> commented that he's able to reproduce the issue on his system, I
>> thought that the problem might be of interest for this mailling list.
>
> I just tried it on a fresh Ubuntu 16.10 install, and it works OK. What
> do you think you're doing differently?