start sandbox without application (runtime debugging)

[Dan Nicholson]

On Tue, Aug 16, 2016 at 9:18 AM, Marco Strigl <mstrigl at suse.de> wrote:
> On 08/16/2016 05:26 PM, Dan Nicholson wrote:
>> On Aug 16, 2016 4:24 AM, "Marco Strigl" <mstrigl at suse.de <mailto:mstrigl at suse.de>> wrote:
>>>
>>> Hello,
>>>
>>> i started working with xdg-app and created an own runtime, commited it into an ostree and wrote a first sample application.
>>> All fine. I can install the runtime and the application. But when i start the application it states:
>>>
>>> execvp hello.sh: No such file or directory
>>>
>>> I tried to "bash" into the sandbox with: xdg-app run --command=bash org.test.hello
>>> But then i get:
>>>
>>> execvp bash: No such file or directory
>>
>> In my experience, this usually means that the dynamic linker can't be found and nothing works. Look around for ld-linux.so.2 (or similar, depends on architecture) in your runtime.
>
> Thanks for pointing me to this. I checked. My dynamic linker is inside the ostree:
>
> /files/lib64/ld-2.19.so
> /files/lib64/ld-linux.so.2 -> ld-2.19.so

Is that actually the right symlink? I believe for x86_64, the ABI
specifies /lib64/ld-linux-x86-64.so.2. E.g.,

$ readelf -l /usr/bin/ls | grep interpreter
      [Requesting program interpreter: /lib64/ld-linux-x86-64.so.2]

ld-linux.so.2 is what's used on i386.

Dan