make kvm_write work

[unix-history] / usr / src / lib / libkvm / kvm_open.3

.\" Copyright (c) 1992 The Regents of the University of California.
.\" All rights reserved.
.\"
.\" %sccs.include.redist.man%
.\"
.\"     @(#)kvm_open.3	5.2 (Berkeley) %G%
.\"
.Dd 
.Dt KVM_OPEN 3
.Os
.Sh NAME
.Nm kvm_open ,
.Nm kvm_openfiles ,
.Nm kvm_close
.Nd initialize kernel virtual memory access
.Sh SYNOPSIS
.Fd #include <kvm.h>
.\" .Fa kvm_t *kd
.br
.Ft kvm_t *
.Fn kvm_open "const char *execfile" "const char *corefile" "char *swapfile" "int flags" "const char *errstr"
.Ft kvm_t *
.Fn kvm_openfiles "const char *execfile" "const char *corefile" "char *swapfile" "int flags" "const char *errbuf"
.Ft int
.Fn kvm_close "kvm_t *kd"
.Sh DESCRIPTION
The functions
.Fn kvm_open
and 
.Fn kvm_openfiles
return a descriptor used to access kernel virtual memory
via the 
.Xr kvm 3
library routines.  Both active kernels and crash dumps are accessible
through this interface.
.Pp
.Fa execfile
is the executable image of the kernel being examined.
This file must contain a symbol table.
If this argument is
.Dv NULL ,
the currently running system is assumed,
which is indicated by
.Dv _PATH_UNIX
in <paths.h>.
.Pp
.Fa corefile 
is the kernel memory device file.  It can be either /dev/mem
or a crash dump core generated by 
.Xr savecore 8 .
If
.Fa corefile
is
.Dv NULL ,
the default indicated by
.Dv _PATH_MEM
from <paths.h> is used.
.Pp
.Fa swapfile
should indicate the swap device.  If
.Dv NULL ,
.Dv _PATH_DRUM
from <paths.h> is used.
.Pp
The
.Fa flags 
argument indicates read/write access as in
.Xr open 2
and applies to only the core file.
Only
.Dv O_RDONLY ,
.Dv O_WRONLY ,
and
.Dv O_RDWR
are permitted.
.Pp
There are two open routines which differ only with respect to 
the error mechanism.
One provides backward compatibility with the SunOS kvm library, while the
other provides an improved error reporting framework.
.Pp
The
.Fn kvm_open
function is the Sun kvm compatible open call.  Here, the
.Fa errstr
argument indicates how errors should be handled.  If it is
.Dv NULL ,
no errors are reported and the application cannot know the 
specific nature of the failed kvm call.
If it is not
.Dv NULL ,
errors are printed to stderr with 
.Fa errstr
prepended to the message, as in
.Xr perror 3 .
Normally, the name of the program is used here.
The string is assumed to persist at least until the corresponding
.Fn kvm_close
call.
.Pp
The
.Fn kvm_openfiles
function provides BSD style error reporting.
Here, error messages are not printed out by the library.
Instead, the application obtains the error message
corresponding to the most recent kvm library call using
.Fn kvm_geterr
(see
.Xr kvm_geterr 3 ).
The results are undefined if the most recent kvm call did not produce
an error.
Since
.Fn kvm_geterr
requires a kvm descriptor, but the open routines return
.Dv NULL
on failure,
.Fn kvm_geterr
cannot be used to get the error message if open fails.
Thus,
.Fn kvm_openfiles
will place any error message in the
.Fa errbuf
argument.  This buffer should be _POSIX2_LINE_MAX characters large (from
<limits.h>).
.Sh RETURN VALUES
The
.Fn kvm_open
and 
.Fn kvm_openfiles
functions both return a descriptor to be used
in all subsequent kvm library calls.
The library is fully re-entrant.
On failure,
.Dv NULL
is returned, in which case
.Fn kvm_openfiles
writes the error message into 
.Fa errbuf .
.Pp
The
.Fn kvm_close
function returns 0 on sucess and -1 on failure.
.Sh BUGS
There should not be two open calls.  The ill-defined error semantics
of the Sun library and the desire to have a backward-compatible library
for BSD left little choice.
.Sh SEE ALSO
.Xr open 2 ,
.Xr kvm 3 ,
.Xr kvm_getargv 3 ,
.Xr kvm_getenvv 3 ,
.Xr kvm_geterr 3 ,
.Xr kvm_getprocs 3 ,
.Xr kvm_nlist 3 ,
.Xr kvm_read 3 ,
.Xr kvm_write 3