Add crash 7.2.6 #1199
Merged
Add crash 7.2.6 #1199
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
[Description][1]: > The core analysis suite is a self-contained tool that can be used to > investigate either live systems, kernel core dumps created from dump > creation facilities such as kdump, kvmdump, xendump, the netdump and > diskdump packages offered by Red Hat, the LKCD kernel patch, the mcore > kernel patch created by Mission Critical Linux, as well as other formats > created by manufacturer-specific firmware. [1]: https://github.com/crash-utility/crash
Fix the [error][1] below.
[BEE] make -j120 install PREFIX=/usr EPREFIX=/usr BINDIR=/usr/bin SBINDIR=/usr/sbin LIBEXECDIR=/usr/libexec SYSCONFDIR=/etc SHAREDSTATEDIR=/var LOCALSTATEDIR=/var LIBDIR=/usr/lib INCLUDEDIR=/usr/include DATAROOTDIR=/usr/share DATADIR=/usr/share INFODIR=/usr/share/info LOCALEDIR=/usr/share/locale MANDIR=/usr/share/man DOCDIR=/usr/share/doc/crash DESTDIR=/dev/shm/bee-root/crash/crash-7.2.6-0/image
/usr/bin/install crash /dev/shm/bee-root/crash/crash-7.2.6-0/image/usr/bin
/usr/bin/install: cannot create regular file '/dev/shm/bee-root/crash/crash-7.2.6-0/image/usr/bin': No such file or directory
make: *** [Makefile:306: install] Error 1
Command exited with non-zero status 2
[1]: https://github.com/crash-utility/crash/pull/37
|
The supposed missing memory at 0xffffffffa0000000 in our crash dumps is the vmalloc area. All physical pages are mapped to virtual pages at 0xffff880000000000 and this is in the crash dump. However, vmalloc() allocates continuous virtual address space and set up the page table to map the physical pages a second time at these virtual adresses. To assist in analyzing this, kdump writes some data into note section in the crash dump file. However, gdb alone does not interpret this information, so 0xffffffffa0000000 is not accessible. One important user of vmalloc is the loader for dynamic modules. So everything stored in sections of loaded modules is not directly available in gdb. This is why so many pointers seem to be invalid when just using gdb on a vmcore. However, "crash" does interpret this additional information and fixes up the address space for gdb: ( list_fs is my own macro to walk the list of file systems ). So this is definitely a useful tool for crash analysis. I'll merge and install on distmaster, because you are on vacation. Thanks. |
Sign in
to join this conversation on GitHub.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.