cpio | cpio library & python - initrd | Download Utils library

Sounds like a broken package. First things, try cleaning it and rebuilding

The last three lines of your Dockerfile are specifying a single command:

Since it seems that you have already downloaded the custom toolchain tarball, why not simply manually install (i.e. un-archive) the custom toolchain, and then choose the appropriate Buildroot options (i.e. for a Pre-installed toolchain)?

For instance I install toolchains at /opt/, and Linaro toolchains under /opt/linaro/. The same toolchain that you're using is installed on my development PC as:

As you can see in strace, the execve command executes as: execve("/bin//nc", ["/bin//nc", "/bin//nc-e //bin/bash -nvlp 4455"], NULL) = 0 It seems to be taking the whole /bin//nc-e //bin/bash -nvlp 4455 as a single argument and thus thinks it's a hostname. In order to get around that, the three argv[] needed for execve() is pushed seperately. argv[]=["/bin/nc", "-e/bin/bash", "-nvlp4455"] These arguments are each pushed into edx, ecx, and ebx. since ebx needs to be /bin/nc, which was already done in the original code. we just needed to push 2nd and 3rd argv[] into ecx and edx and push it into stack. After that we just copy the whole stack into ecx, and then xor edx,edx to set edx as NULL.

Here is the correct solution:

Looking at the log, there's not much info, but I can assume from it that you were using WSL or something similar on Windows, not using an actual Ubuntu device. The reason why buildozer doesn't work, I don't know, the log doesn't go far back enough for me to find out, but it is very likely that is because WSL is not a full-fledged Linux distribution

The solution for me was to use an online virtual machine called Google Colaboratory

Press cancel to the popup to open a new notebook

Initialize the VM by pressing Connect in the top-right part of the page

Then add a new Code Cell by pressing +Code

To set up buildozer and other commands, paste into the cell and press the play icon

From https://www.gnu.org/software/coreutils/manual/html_node/dd-invocation.html#dd-invocation

‘skip=n’

Skip n ‘ibs’-byte blocks in the input file before copying. If ‘iflag=skip_bytes’ is specified, n is interpreted as a byte count rather than a block count.

So, if you didn't have iflag=skip_bytes in your bash script, you'd have to multiply $start by the block size before seeking. But since the iflag=skip_bytes is there, no multiplication is necessary and you only need to seek by $start bytes.

socket is a python builtin module, not something to install via pip.

I have also attempted to compile the app without socket as a dependency, which compiles but crashes the mobile app when any socket command is run

What makes you think the crash is due to missing the socket module?

A segmentation fault happens when the code try to access a memory region that is not available.

Accessing an array out of bounds doesn't means that the memory before or after the area occupied by the array is not available: The compiler or the runtime usually put all varibales or data in general in a given block of memory. If your array is the last item of such a memory block, the accessing it with a to big index will produce a Segmentaion Fault but is the array is in the middle of the memory block, you will just access memory used for other data, giving unexpected result and undefined behavior.

If the array (In may example, but valid for anything) is written, accessing available memory will not produce a segmentation fault but will overwrite something else. It may produce unexpected results or crash or segmentation fault later! This kind of bug is frequently very difficult to find because the unexpected result/behavior looks completely independent of the root cause.

The problem solved just by deleting the /etc/php.d/ directory. Then reinstall PHP.