forked from tarantool/tarantool
-
Notifications
You must be signed in to change notification settings - Fork 0
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
Architecture Specifications
- Server architecture
- Feature specifications
- What's in a good specification
- Functional indexes
- Space _index structure
- R tree index quick start and usage
- LuaJIT
- Vinyl
- SQL
- Testing
- Performance
How To ...?
- ... 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 Lua state with GDB
- ... generate new bootstrap snapshot
- ... use Address Sanitizer
- ... collect a coredump
Lua modules
Useful links