我最近正在迁移一个项目以使用新的优化库。一切都在DEV服务器上测试得很好。但是,在LIVE中实现时,会发生一些核心转储。通过使用dbx工具,它显示信号ILL和信号SEGV错误,但很难找到coredump的确切位置。
我已经编译了DEV服务器中的所有内容,只是将可执行文件部署到LIVE。为什么LIVE和DEV会出现这种不同的行为?
在这里找不到类似的问题所以请帮忙。下面是两个错误的例子。我试图追踪指定的核心转储位置,但没有解释原因。
**error 1:**
core file header read successfully
Reading ld.so.1
Reading libcrypt_d.so.1
Reading libnsl.so.1
Reading libsocket.so.1
Reading libgen.so.1
Reading libkstat.so.1
Reading libdl.so.1
Reading libsched.so.1
Reading libaio.so.1
Reading librt.so.1
Reading libm.so.2
Reading libthread.so.1
Reading libCrun.so.1
Reading libc.so.1
Reading libmd.so.1
Reading libc_psr.so.1
WARNING!!
A loadobject was found with an unexpected checksum value.See help core mismatch for details, and run proc -map
to see what checksum values were expected and found.
dbx: warning: **Some symbolic information might be incorrect.
t@1 (l@1) program terminated by signal ILL (illegal opcode)
0xffffffffffffffff: <bad address 0xffffffffffffffff>
(dbx) exit**
**error 2:**
core file header read successfully
Reading ld.so.1
Reading libcrypt_d.so.1
Reading libnsl.so.1
Reading libsocket.so.1
Reading libgen.so.1
Reading libkstat.so.1
Reading libdl.so.1
Reading libsched.so.1
Reading libaio.so.1
Reading librt.so.1
Reading libm.so.2
Reading libthread.so.1
Reading libCrun.so.1
Reading libc.so.1
Reading libmd.so.1
Reading libc_psr.so.1
WARNING!!
A loadobject was found with an unexpected checksum value.
See help core mismatch for details, and run proc -map
to see what checksum values were expected and found.
dbx: warning: **Some symbolic information might be incorrect.
t@1 (l@1) program terminated by signal SEGV (no mapping at the fault address)
0x03b2d8cc: seekoff+0x01c4: ld [%l4 + 32], %i3**
Current function is
dbx: warning: can't find file "/opt/IMP/BUILD/CITOS_ENGINE_YPENG/src/make/automicro/../../include/entity/Voyage.hh"
dbx: warning: see `help finding-files'