0

How to view these core files?These files take up a lot of memory, I want to close the generation of these files.

enter image description here

These files appear in the /usr/local/nebula path. For example:

core.ruby.12759.16496723591
core.ruby.128288.1649672928
core.ruby.127623.1643934031
...
foesa Yang
  • 26
  • 5
  • It means the binary crashed(for many times). Read more from https://stackoverflow.com/questions/5115613/core-dump-file-analysis – Wey Gu Dec 28 '22 at 06:38
  • In most cases you just describe on how you triggerred such situation and report this in NebulaGraph github issues. – Wey Gu Dec 28 '22 at 06:39
  • Are these files in your machine's filesystem? If so, could you please [edit] to specify what path you have found these files in? – starball Jan 05 '23 at 03:14

1 Answers1

0

You can use the gdb tool to view these core files.

  1. Check the Core file process name, pid is usually a numeric value. 
    $ file core.<pid>
  2. Use gdb to debug. 
    $ gdb <process.name> core.<pid>
  3. View the contents of the file. 
    $(gdb) bt

For example:

$ file core.1316027
core.1316027: ELF 64-bit LSB core file, x86-64, version 1 (SYSV), SVR4-style, from '/home/workspace/fork/nebula-debug/bin/nebula-metad --flagfile /home/k', real uid: 1008, effective uid: 1008, real gid: 1008, effective gid: 1008, execfn: '/home/workspace/fork/nebula-debug/bin/nebula-metad', platform: 'x86_64'
$ gdb /home/workspace/fork/nebula-debug/bin/nebula-metad core.1316027
$(gdb) bt
#0  0x00007f9de58fecf5 in __memcpy_ssse3_back () from /lib64/libc.so.6
#1  0x0000000000eb2299 in void std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >::_M_construct<char*>(char*, char*, std::forward_iterator_tag) ()
#2  0x0000000000ef71a7 in nebula::meta::cpp2::QueryDesc::QueryDesc(nebula::meta::cpp2::QueryDesc const&) ()
...
黄凤仙
  • 107
  • 5