We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
I have to kill my SSH session to get control back. I've done it twice and it reproduces.
ls -lai works in root's homedir.
The text was updated successfully, but these errors were encountered:
Thank you for letting me know. Apparently you hit unimplemented part in readlink(2):
readlink(2)
kerla/kernel/syscalls/readlink.rs
Line 25 in 7c4f67e
Sorry, something went wrong.
917c8e8
Embed a backtrace into Error in debug build
72554b4
It helps where an error is constructed: [ 0.585] [7:curl] syscall: close(ffffffffffffffff, 0, 0, 0, 0, 0) [ 0.585] WARN: close: error: EBADF: This error originates from: #1: ffff800000184219 kerla::printk::capture_backtrace()+0x79 #2: ffff8000001dbb13 kerla::result::Error::new()+0x23 #3: ffff8000001dc0e7 <kerla::result::Error as c...la::result::Errno>>::from()+0x17 #4: ffff800000211177 <T as core::convert::Into<U>>::into()+0x17 #5: ffff8000001fcb55 kerla::fs::opened_file::OpenedFileTable::close()+0xa5 #6: ffff80000010b124 kerla::syscalls::close::<i...yscallHandler>::sys_close()+0xa4 #7: ffff80000011bf62 kerla::syscalls::SyscallHandler::do_dispatch()+0x4e62 #8: ffff8000001168fc kerla::syscalls::SyscallHandler::dispatch()+0x1ac
No branches or pull requests
I have to kill my SSH session to get control back. I've done it twice and it reproduces.
ls -lai works in root's homedir.
The text was updated successfully, but these errors were encountered: