Man page or keyword search:   man All Sections 1 - General Commands 2 - System Calls 3 - Subroutines, Functions 4 - Special Files 5 - File Formats 6 - Games and Screensavers 7 - Macros and Conventions 8 - Maintenence Commands 9 - Kernel Interface New Commands Server 4.4BSD AIX Alpinelinux Archlinux Aros BSDOS BSDi Bifrost CentOS Cygwin Darwin Debian DigitalUNIX DragonFly ElementaryOS Fedora FreeBSD Gentoo GhostBSD HP-UX Haiku Hurd IRIX Inferno JazzOS Kali Knoppix LinuxMint MacOSX Mageia Mandriva Manjaro Minix MirBSD NeXTSTEP NetBSD OPENSTEP OSF1 OpenBSD OpenDarwin OpenIndiana OpenMandriva OpenServer OpenSuSE OpenVMS Oracle PC-BSD Peanut Pidora Plan9 QNX Raspbian RedHat Scientific Slackware SmartOS Solaris SuSE SunOS Syllable Tru64 UNIXv7 Ubuntu Ultrix UnixWare Xenix YellowDog aLinux   9087 pages apropos Keyword Search (all sections) Output format html ascii pdf view pdf save postscript

KVM(3)			 BSD Library Functions Manual			KVM(3)

NAME
     kvm — kernel memory interface

LIBRARY
     Kernel Data Access Library (libkvm, -lkvm)

DESCRIPTION
     The kvm library provides a uniform interface for accessing kernel virtual
     memory images, including live systems and crash dumps.  Access to live
     systems is via /dev/mem while crash dumps can be examined via the core
     file generated by savecore(8).  The interface behaves identically in both
     cases.  Memory can be read and written, kernel symbol addresses can be
     looked up efficiently, and information about user processes can be gath‐
     ered.

     kvm_open() is first called to obtain a descriptor for all subsequent
     calls.

FILES
     /dev/mem  interface to physical memory

COMPATIBILITY
     The kvm interface was first introduced in SunOS.  A considerable number
     of programs have been developed that use this interface, making backward
     compatibility highly desirable.  In most respects, the Sun kvm interface
     is consistent and clean.  Accordingly, the generic portion of the inter‐
     face (i.e., kvm_open(), kvm_close(), kvm_read(), kvm_write(), and
     kvm_nlist()) has been incorporated into the BSD interface.	 Indeed, many
     kvm applications (i.e., debuggers and statistical monitors) use only this
     subset of the interface.

     The process interface was not kept.  This is not a portability issue
     since any code that manipulates processes is inherently machine depen‐
     dent.

     Finally, the Sun kvm error reporting semantics are poorly defined.	 The
     library can be configured either to print errors to stderr automatically,
     or to print no error messages at all.  In the latter case, the nature of
     the error cannot be determined.  To overcome this, the BSD interface
     includes a routine, kvm_geterr(3), to return (not print out) the error
     message corresponding to the most recent error condition on the given
     descriptor.

SEE ALSO
     kvm_close(3), kvm_getargv(3), kvm_getenvv(3), kvm_geterr(3),
     kvm_getkernelname(3), kvm_getloadavg(3), kvm_getlwps(3), kvm_getprocs(3),
     kvm_nlist(3), kvm_open(3), kvm_openfiles(3), kvm_read(3), kvm_write(3)

BSD			      September 14, 2011			   BSD

                             _         _         _ 
                            | |       | |       | |     
                            | |       | |       | |     
                         __ | | __ __ | | __ __ | | __  
                         \ \| |/ / \ \| |/ / \ \| |/ /  
                          \ \ / /   \ \ / /   \ \ / /   
                           \   /     \   /     \   /    
                            \_/       \_/       \_/ 

Vote for polarhome