运行arm-elf-gcc编译代码时出现seg错误
使用 MacPorts，我刚刚在 MacBook Pro 上安装了 arm-elf-gcc。这工作完美无缺，一切似乎都运行良好。
然而，在用 C 和 C++ 编译一个简单的 hello world 测试程序并尝试在目标板（运行 Debian Linux 的基于 ARM9 的板）上运行后，它们立即出现段错误。
我对如何调试这个有点困惑，因为目标板可用的工具有限并且没有 gdb。我已经使用 Linux 托管的交叉编译器成功构建并运行了其他代码，因此它应该可以工作。
有什么想法吗？
按照我构建并运行 gdbserver 的建议，我在主机上的 gdb 中得到以下信息：
程序收到信号 SIGSEGV，分段错误。 0x00000000 在 ?? ()
我认为这可能是标准 c 库的问题，所以我删除了所有调用，只有一个返回 0 的空 main，它是用 -Wall -g hello-arm.cpp -static 编译的。作为测试，我使用 Linux 托管的交叉编译器编译了相同的源代码，它运行和退出都很好。我能看到的唯一区别是 Linux 编译版本的大小超过两倍，以及 file 命令的输出差异：
arm-elf-gcc：ELF 32 位 LSB 可执行文件，ARM，版本1，静态链接，未剥离
arm-*-linux：ELF 32位LSB可执行文件，ARM，版本1，静态链接，适用于GNU/Linux 2.4.18，未剥离
Using MacPorts i have just installed arm-elf-gcc on to my MacBook Pro. This worked flawlessly and all seems to run fine.
However, after compiling a simple hello world test program in C and C++ and trying to run either on the target board (an ARM9 based board running Debian Linux) they immediately seg fault.
I'm a bit stuck as how to go about debugging this, as the target board has limited tools available and no gdb. I have successfully built and run other code using a Linux hosted cross compiler so it should work.
Any ideas?
Following the suggestion I have built and run gdbserver, I get the following in gdb on the host:
Program received signal SIGSEGV, Segmentation fault.
0x00000000 in ?? ()
I thought it may be a problem with the standard c libs so I removed any calls and have just an empty main that return 0, it is compiled with -Wall -g hello-arm.cpp -static. As a test I compiled the same source with a Linux hosted cross compiler and it runs and exits fine. The only difference I can see is the that Linux compiled version is over twice the size and the difference in output from the file command:
arm-elf-gcc: ELF 32-bit LSB executable, ARM, version 1, statically linked, not stripped
arm-*-linux: ELF 32-bit LSB executable, ARM, version 1, statically linked, for GNU/Linux 2.4.18, not stripped
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
在这种情况下，通常的调试方法是在目标板上运行 gdbserver，并通过主机上运行的 gdb 连接到它（通过以太网）。
或者，您可以尝试将 Mac 编译的“Hello World”程序中的程序集与（工作的）Linux 编译的程序集进行比较，看看有什么不同。
The usual method of debugging in this situation is to run gdbserver on the target board, and connect to it (via ethernet) with gdb running on a host computer.
Alternately, you could try comparing the assembly in a Mac-compiled "Hello World" program and a (working) Linux-compiled one to see what's different.
经过几天的研究，我开始对嵌入式编译器有了更多的了解。我不太确定通过 MacPorts 安装的 arm-elf-gcc 和我在 Linux 机器上安装的 arm-unknown-linux 工具链之间的区别。我刚刚看到一个 pdf 标题为“GNU 简介编译器”，其中包含以下段落：
因此，当我稍后回到我的开发机器时，我将确定与 Linux 构建链接的库并将它们添加到 arm-elf-gcc 构建中。
当我有更多信息时，我会更新此内容，但我只是想记录我的发现，以防其他人遇到这些问题。
After digging around for a couple of days I am starting to understand a bit more about embedded compilers. I wasn't really sure of the difference between arm-elf-gcc installed via MacPorts and the arm-unknown-linux toolchain I had installed on my Linux box. I just came across a pdf titled "An introduction to the GNU compiler" which contains the following paragraph:
So when I get back to my dev machine later I will determine the libraries linked in with the Linux build and add them to the arm-elf-gcc build.
I'll update this when I have more information but I just want to document my findings in case any one else has these problems.