Does C ++ have memory protection? Actually:
Http://en.wikipedia.org/wiki/Buffer_overflow_protection
This can only protect the buffer on the stack, but it is already very useful.
The probability of writing callstack out of bounds is much lower.
Reminder: If callstack does not have valid information, it is more likely that the Environment version does not match. It is rare to write down callstack.
In addition, use the LDD command to check whether the environments of the two machines are consistent. Note that the shared library address:
LDD httpd
Libz. so.1 =>/usr/lib64/libz. so.1 (0x00000033f7e00000)
Libm. so.6 =>/lib64/libm. so.6 (0x00000033f7200000)
LDD httpd
Libz. so.1 =>/usr/lib64/libz. so.1 (0x0000003b2cc00000)
Libm. so.6 =>/lib64/libm. so.6 (0x0000003b2c400000)
If the dynamic library loading addresses of the two machines are inconsistent, the core file cannot be debugged across machines.