Re: compat_linux failures due to execve, openat, etc.

[Kevin Bloom <ktnb%posteo.net@localhost>]

Robert Swindells <rjs%fdy2.co.uk@localhost> wrote:

> 
> Kevin Bloom <ktnb%posteo.net@localhost> wrote:
> > Robert Swindells <rjs%fdy2.co.uk@localhost> wrote:
> >> 
> >> Kevin Bloom <ktnb%posteo.net@localhost> wrote:
> >> > I've tried settings LD_LIBRARY_PATH and LD_PRELOAD to no avail. I
> >> > can't seem to come up with any other hacks to try to convince nix-env
> >> > everything is okay. Any ideas?
> >> 
> >> Have you tried running ktrace(1) on a non-nix Linux binary?
> >> 
> >> One that I just tried also returns an error from execve but carries on
> >> after that and works correctly.
> >
> > Hmm, you're right. I ran nodeJS just fine and see the same errors.
> > I wonder _what_ exactly is causing the nix-env program to not run
> > all the way. When I run it, I get these errors in the STDOUT:
> > GC warning: pthread_setname_np failed
> > error: setting death signal: Function not implemented
> >
> > When I look through the ktrace of nix-env, I don't see anything
> > obvious. It might be that I just don't know what to look for too.
> > Do you have any general rules of thumb when looking at this sort
> > of thing?
> 
> UTSL
> 
> Look at the sources to whatever version of glibc is in nix and see what
> pthread_setname_np() is doing.
> 
> You could compile tst-setgetname.c into a single executable on Linux,
> copy that onto your NetBSD system and try it out.
> 
> You do have an emulated Linux procfs mounted as well as native /proc?
> 
> Maybe we need to extend the proc emulation to add some extra things.

Minor update: I found the GC warnings in ktrace and see this a few
lines above it:
10480  10480 nix-env  CALL  #157 (unimplemented prctl)
10480  10480 nix-env  RET  #157 (unimplemented prctl) -1 errno -38 Too many processes

Could this prctl be something that isn't implemented in compat_linux?