Reported by a Funtoo user and independently confirmed by me - it appears that sandbox-1.9 does not properly ptrace static binaries and thus if something such as coreutils is compiled with USE="static", subsequent /bin/install calls made inside sandbox will fail. See attached output. Note in the attached output that the "C:" line from the ACCESS VIOLATION SUMMARY has a space between "/var" and "tmp", where it appears a "/" should be. This may indicate a string-handling bug in the static binaries support in sandbox-1.9. Reproducible: Always Steps to Reproduce: 0. ensure sandbox-1.9 is installed 1. USE="static" emerge coreutils 2. emerge <any package that uses /bin/install (pretty much everything)> 3. view sandbox violation.
Created attachment 188115 [details] failed sandbox output 1
Created attachment 188117 [details] failed sandbox output 2 (drobbins)
there is nothing wrong with the string handling. the space is because coreutils modifies its argv.
OK, good to know. Is the issue then that the static sandbox stuff uses argv to do its magic? Or some other as-yet-undetermined bug in sandbox?
i defined the bug in the new summary. only thing remaining is for me to ponder how to fix it without duplicating code.
OK, thanks for looking into this, I do appreciate it. Now I can get back to riding my invisible pony around the house.
fixed in sandbox-2.0 http://git.overlays.gentoo.org/gitweb/?p=proj/sandbox.git;a=commitdiff;h=70f148095b7b9acd4e8329da0766aadc88b017d8
Nice - I will give it a shot.
