**** BEGIN LOGGING AT Tue May 30 03:00:05 2017 May 30 06:33:38 Morning! May 30 06:33:49 Back from the island :) May 30 06:46:15 welcome back Tofe May 30 06:46:43 which island? May 30 06:55:22 saidinesh5: Ireland May 30 06:56:56 saidinesh5: your link has expired I think May 30 08:20:32 Ahh.. will get a new link May 30 08:20:43 basically i was having odd issues starting the container/chrooting into it.. May 30 08:21:41 chroot fails with sigabort . and if i overlay my /system/bin/sh on top of the /system/bin/sh from the android img im trying to chroot into, i am able to chroot but then weird things happen inside the chroot May 30 08:22:03 ls fails but cd works inside the chroot.. May 30 08:50:08 Morning! May 30 08:50:16 Tofe: Welcome back! May 30 08:53:32 Herrie|Pre3: thanks! May 30 08:54:42 saidinesh5: if you use android's sh in your chroot, just be sure the libs that are being used are consistent (not a weird mix of patched and non-patched libs) May 30 08:55:22 saidinesh5: ls is an external executable, not cd May 30 08:55:37 any specific libs Tofe? i am trying to use android's libEGL blobs and so overlaid their dependenies on top of chroot.. May 30 08:56:11 saidinesh5: sh and ls mainly rely on bionic, maybe one or two more basics May 30 08:57:16 Ah May 30 08:57:42 https://bpaste.net/show/37690bc9bb9f these are the libs im overlaying May 30 09:23:11 saidinesh5: looks ok, but frankly it's hard to tell May 30 09:23:52 if you could have a look at /proc/$(pidof ls)/maps and see what ls is using... but I don't know how you'lll be able to catch that **** ENDING LOGGING AT Wed May 31 03:00:02 2017