termux-chroot segfaults on aarch64 #378
Labels
bug report
Something is not working properly
Comments
|
What is the model, Android version and Linux kernel version ( Related: #258 (the Nexus 9 kernel does not have the necessary suport compiled in, could it be the same thing here)? |
|
Model: Sony Xperia X |
|
It doesn't actually crash completely. I am still in some kind of non-working proot shell |
|
What shell do you use (As chosen with Looks like Your shell has started something else on startup before crashing, so it doesn't look like "pure" |
|
I am running zsh. I figured out that the segfault was tmux, for which I run a command from in my .zshrc,. Running termux-chroot from bash seems to work running with zsh (even without .zshrc) still gives me the same error. Also many programms don't work under |
|
Still couldn't reproduce; possibly something specific to device's libc or linker. Could I ask for result of |
Seems something is missing from that command |
You missed |
|
Oh, sorry. Alright, I ran this command, but it doesn't halt. It's not supposed to run for more than 2 minutes right? |
|
No, it shouldn't on fixed version (though it does on official Termux version from apt, providing trace with just (doesn't work with Or does it hang still on "fixed" version? |
|
Yes it's still hangs on the fixed version. No trace.txt is generated. |
|
So it looks like I cannot debug remotely further, so I'd ask for |
|
|
Still wasn't able to reproduce, even with these libraries, I think there's something in kernel, I think that following trace would be helpful (this time running |
michalbednarski
added a commit
to michalbednarski/termux-packages
that referenced
this issue
Aug 17, 2016
|
Looks like |
|
Still doesn't work, but I think it's something else that broke. ~/proot-aarch64-debug 1 $ strace -vs50000 -o trace.txt ./proot2 -v 6 make |
|
It also seems to install the first version fine. To test this I uninstalled proot and then just installed your version, rather than updating from the apt one. |
|
The "CANNOT LINK EXECUTABLE" above means I accidentaly uploaded version requiring debug build of |
|
Turns out that ELFs in /data/.../bin on build host are not ones ready to be executed |
|
Alright, here's the trace.txt and the output |
ghost
locked and limited conversation to collaborators
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
This happens on my aarch64 phone, but it works on my arm phone.
The text was updated successfully, but these errors were encountered: