gem5 syscall emulation arm C hello world 因“致命:syscall gettid (#224) unimplemented"而失败 [英] gem5 syscall emulation arm C hello world fails with "fatal: syscall gettid (#224) unimplemented"

查看:21
本文介绍了gem5 syscall emulation arm C hello world 因“致命:syscall gettid (#224) unimplemented"而失败的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我在 gem5 中遇到以下错误.这仅在 ARM 中发生.在 X86 中,我看到一些系统调用被忽略,但没有一个会导致致命错误.

I am having the following error in gem5. This happens in ARM only. With X86 I see some syscalls being ignored but none causing a fatal error.

tomas@ubuntu:~/gem5$ ./build/ARM/gem5.opt configs/example/arm/starter_se.py ../tests_gem5/hello
gem5 Simulator System.  http://gem5.org
gem5 is copyrighted software; use the --copyright option for details.

gem5 compiled Jul  9 2018 17:09:01
gem5 started Jul  9 2018 18:07:37
gem5 executing on ubuntu, pid 5064
command line: ./build/ARM/gem5.opt configs/example/arm/starter_se.py ../tests_gem5/hello

info: 1. command and arguments: ['../tests_gem5/hello']
Global frequency set at 1000000000000 ticks per second
warn: DRAM device capacity (8192 Mbytes) does not match the address range assigned (1024 Mbytes)
warn: DRAM device capacity (8192 Mbytes) does not match the address range assigned (1024 Mbytes)
0: system.remote_gdb: listening for remote gdb on port 7000
info: Entering event queue @ 0.  Starting simulation...
fatal: syscall openat (#322) unimplemented.
Memory Usage: 2246296 KBytes

我在 gem5 的常见问题解答中找到了 this 答案.但是现在它显示了这个错误:

I found this answer in gem5's FAQ. But now it shows this error:

warn: ignoring syscall openat(...)
FATAL: kernel too old
warn: ignoring syscall rt_sigprocmask(...)
      (further warnings will be suppressed)
fatal: syscall gettid (#224) unimplemented.

我正在使用这个在 Ubuntu 18.04 中编译:

I am compiling in Ubuntu 18.04 using this:

arm-linux-gnueabi-gcc hello.c -o hello -static -DUNIX

有没有人找到一种方法来编译一个简单的 hello world,针对 ARM,不使用 gem5 不支持的系统调用?有预编译的例子,所以一定有办法.

Has anyone found a way to compile a simple hello world, targeting ARM, that doesn't use syscalls not supported by gem5? There are pre-compiled examples so there must be a way.

推荐答案

更新:x86、arm 和 aarch64 C hello world 正在使用 Ubuntu 18.04 预打包工具链,请参阅:如何在 gem5 中编译和运行可执行文件带 se.py 的系统调用仿真模式?

update: x86, arm and aarch64 C hello world is working on Ubuntu 18.04 pre-packaged toolchain, see: How to compile and run an executable in gem5 syscall emulation mode with se.py?

致命:内核太旧"之前已在以下位置询问:如何解决致命:内核太旧"在系统调用仿真 SE 模式下运行 gem5 时?

"FATAL: kernel too old" has been previously asked at: How to solve "FATAL: kernel too old" when running gem5 in syscall emulation SE mode?

如该页面所述,该消息来自 glibc 健全性检查,而 ct-ng 是克服它的最明智的方法.

As explained in that page, that message comes from a glibc sanity check, and ct-ng is the sanest approach to overcome it.

至于未实现的系统调用,我不知道为什么 x86 会忽略它们并导致 arm 崩溃,但如果您给出 x86 系统调用被忽略的消息,应该很容易在源代码中找到它.

As for the unimplemented syscalls, I don't know why x86 ignores them and arm blows up, but it should be easy to grep that up in the source if you give the x86 syscall ignored message.

但是这种爆破行为似乎是明智的:当你的程序试图运行一个未实现的系统调用时,你怎么能期望它正常工作呢?

But the blow up behavior does seem sensible: how can you expect your program to work properly when it tries to run an unimplemented syscall?

大多数系统调用在两个架构中都未实现,如下所示:

Most syscalls are unimplemented in both archs as can be seen at:

所以,我只看到两个明智的解决方案:

So, I only see two sensible solutions:

  • 实现系统调用,这对他们中的大多数人来说都很容易,然后给 gem5 发送一个补丁
    • 看看其他 Arch 是否通过 grepping 实现了它,有时另一个 Arch 已经实现了,你只需要写出来
    • 您也可以尝试忽略系统调用,TODO:ARM 中有什么好的方法吗?但您必须非常确定这不会有什么影响.

    这篇关于gem5 syscall emulation arm C hello world 因“致命:syscall gettid (#224) unimplemented"而失败的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆