Any progress as solving #650234? Reads like the problem has been identified, but no solution has come up. I've got no idea if any possible solutions are visible...
One thought, in wrapping execve(), use "<chroot>/lib/ld-linux.so.2" as the filename. Push "<chroot>/lib/ld-linux.so.2" on to argv[], then use the filename as argv[1]. This means invoked programs will always see their full pathname as argv[0], but ensures the chroot's loader is used. Another thought, perhaps try loading ld.so's version of libc? I'd seriously worry about chroot programs needing a later version, but might handle easier cases. -- (\___(\___(\______ --=> 8-) EHM <=-- ______/)___/)___/) \BS ( | ehem+sig...@m5p.com PGP F6B23DE0 | ) / \_CS\ | _____ -O #include <stddisclaimer.h> O- _____ | / _/ 2477\___\_|_/DC21 03A0 5D61 985B <-PGP-> F2BE 6526 ABD2 F6B2\_|_/___/3DE0 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org