Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update 0.FAQ.md #1824

Merged
merged 3 commits into from
Dec 23, 2022
Merged
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
13 changes: 13 additions & 0 deletions docs-2.0/20.appendix/0.FAQ.md
Original file line number Diff line number Diff line change
Expand Up @@ -395,6 +395,19 @@ The dmp file is an error report file detailing the process exit information, whi
```
$(gdb) bt
```
For example:
```bash
$ file core.624
foesa-yang marked this conversation as resolved.
Show resolved Hide resolved
core.624: ELF 64-bit LSB core file x86-64, version 1 (SYSV), SVR4-style, from '/usr/local/nebula', real uid: 0, effective uid: 0, real gid: 0, effective gid: 0, execfn: '/usr/local/nebula', platform: 'x86_64'

$ gdb /usr/local/nebula core.624

$(gdb) bt
...
warning: File "/usr/lib64/libthread_db-1.0.so" auto-loading has been declined by your `auto-load safe-path' set to "$debugdir:$datadir/auto-load:/usr/share/gdb/auto-load".
...
```

If the user is not sure about the information related to the dmp printout, you can post the printout on the [NebulaGraph Forum](https://github.com/vesoft-inc/nebula/discussions) with the operating system version, hardware configuration, error logs before and after the Core file was generated and actions that may have caused the error for help.

## About connections
Expand Down