Subject: Re: suggested alteration to kvm_open() and kvm_openfiles()
To: None <>
From: Christos Zoulas <>
List: tech-kern
Date: 09/14/2002 20:30:53
In article <>,
Andrew Brown <> wrote:

No, that makes more sense to me [to look in the booted kernel first].


>currently, with these two libkvm functions:
>     kvm_t *
>     kvm_open(const char *execfile, const char *corefile, char *swapfile,
>             int flags, const char *errstr);
>     kvm_t *
>     kvm_openfiles(const char *execfile, const char *corefile, char *swapfile,
>             int flags, char *errbuf);
>if a null pointer is passed for execfile, the man page states that:
>     If this argument is NULL, the currently running system is
>     assumed, which is indicated by _PATH_UNIX in <paths.h>.
>would anyone find it particularly egregious if this was modified
>slightly so that a null pointer caused it to default to
>machdep.booted_kernel, and then to fall back to _PATH_UNIX if the
>former was not found?
>|-----< "CODE WARRIOR" >-----|
>             * "ah!  i see you have the internet
> (Andrew Brown)                that goes *ping*!"
>       * "information is power -- share the wealth."