-
Notifications
You must be signed in to change notification settings - Fork 387
How to debug core from different OS
Aleksandr Lyapunov edited this page Nov 2, 2016
·
2 revisions
Sometimes customers have a crash and can provide you a core file and everything you ask for, but gdb shows nothing but "???". Here's the instruction how fix the problem and debug the core file.
- Request for core file and tarantool binary.
- Run 'gdb ' and type 'info sharedlibrary'
- Request for all libraries listed in (2) and place it to, for instance, 'lib' folder near core and binary. Use subfolders (e.g. ./lib/lib64) for libraries that listed with subfolders (e.g. /lib64/libc.so.6)
- Run 'gdb' without parameters and type a script:
set solib-absolute-prefix ./lib
file <binary>
core <core>
bt
- C coding guidelines ↗
- Lua coding guidelines ↗
- Python coding guidelines ↗
- Maintainer's guide
- Debugging
Architecture
- Server architecture
- R tree index quick start and usage
- LuaJIT
- Vinyl
- Vinyl Architecture
- Vinyl Disk Layout
- Vinyl math
- Vinyl Cookbook
- Bullet1
- SQL
- Appserver modules
- Testing
- Performance
- Privileges and Access control
How To ...?
- ... configure build system
- ... add new fuzzers
- ... build RPM or Deb package using packpack
- ... calculate memory size
- ... debug core dump of stripped tarantool
- ... debug core from different OS
- ... debug fuzzer
- ... generate new bootstrap snapshot
- ... use Address Sanitizer
- ... collect a coredump
- ... generate luacov report for builtin module
- ... verify modified lua files via luacheck
- ... verify Lua files in third_party?
- ... rerun failed jobs
- ... update a third party repository
- Fix wrong decimal indexing after upgrade to 2.10.1
- Caveats when upgrading a cluster on Tarantool 1.6
- Fix illegal field type in a space format when upgrading to 2.10.4
Useful links