Sorry I didn’t mean to say that we shouldn’t have this in snapd, what I’m specifically curious about is:
How does it not work? Can you provide me with an example of it not working?
Yes but we don’t want to have every snap author have to do this as it is tedious and cumber-some. The reason we included strace inside snapd with --strace=... was that there are certain syscalls that basically cause the exec-chain to hang when they are not excluded, so we exclude those when folks run with snap run --strace=....
If there are similar things with ltrace, then it makes sense I think to include some form of ltrace support in snapd.
Hello, I’m also interested in the native support of ltrace as strace’s output doesn’t specifically point out the library function(s) I need to override in the case of the snapped application hardcoding some of the paths.
In my case, the call seems to be terminated with the following message prematurely: