对 gcc -static 选项或其在虚拟机中的行为感到困惑

Question

我写了一个简单的 c 程序 try.c

#include <stdlib.h>
int main() {return 0;}

然后我尝试用下面的shell脚本编译并运行它

CFLAGS='-Wpedantic -Wall -Wextra -Werror -std=c89'
gcc -o try  ${CFLAGS}  try.c -static
valgrind ./try -v --track-origins=yes

然后输出很混乱：

==16641== Memcheck, a memory error detector
==16641== Copyright (C) 2002-2015, and GNU GPL'd, by Julian Seward et al.
==16641== Using Valgrind-3.11.0 and LibVEX; rerun with -h for copyright info
==16641== Command: ./try -v --track-origins=yes
==16641== 
==16641== Conditional jump or move depends on uninitialised value(s)
==16641==    at 0x419349: _int_free (in  /home/su/ca/hw/1_try/try_static/trytrytry/try)
==16641==    by 0x41D296: free (in    /home/su/ca/hw/1_try/try_static/trytrytry/try)
==16641==    by 0x46CCAE: fillin_rpath (in /home/su/ca/hw/1_try/try_static/trytrytry/try)
==16641==    by 0x46D57A: _dl_init_paths (in /home/su/ca/hw/1_try/try_static/trytrytry/try)
==16641==    by 0x44282B: _dl_non_dynamic_init (in /home/su/ca/hw/1_try/try_static/trytrytry/try)
==16641==    by 0x443557: __libc_init_first (in /home/su/ca/hw/1_try/try_static/trytrytry/try)
==16641==    by 0x400B77: (below main) (in /home/su/ca/hw/1_try/try_static/trytrytry/try)

但是，如果我删除选项“-static”，一切都会顺利进行。我在ubuntu 16.04（虚拟机）和ubuntu 14.04（虚拟机）上试过了可能和虚拟机有关？

Answer 1

此错误是 Valgrind 可能 suppresses 默认调用堆栈的一部分。抑制特定于调用所属的共享库（即 libc）——因此将程序构建为静态可执行文件会阻止 Valgrind 识别它应该忽略此错误。

无论如何，这个错误是 libc 初始化代码的内部错误，因此您应该忽略它。

对 gcc -static 选项或其在虚拟机中的行为感到困惑

Confused about gcc -static option or its behavior in virtual machine

c

gcc

valgrind

static-libraries

static-linking