Date: Thu, 6 Jan 2005 22:05:31 -0800 From: Pascal Hofstee <caelian@gmail.com> To: "Christian S.J. Peron" <csjp@sqrt.ca> Cc: freebsd-hackers@freebsd.org Subject: Re: GNUstep and libkvm Message-ID: <d8a0b762050106220559f630a6@mail.gmail.com> In-Reply-To: <20050107051952.A61748@stf01.seccuris.com> References: <d8a0b76205010618212e484cf4@mail.gmail.com> <20050107051952.A61748@stf01.seccuris.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, 7 Jan 2005 05:19:52 +0000, Christian S.J. Peron <csjp@sqrt.ca> wrote: > iirc, kvm_getargv() can (and does first) use a sysctl to retrieve > it's data. kvm_getenvv() requires procfs because > /proc/<pid>/mem is currently the more simpler to read a virtual > memory address in the context of the process. > > We are looking at implementing a similar mechanism to the "argv" > ps_strings for process environment to get rid of the procfs requirement. > > pjd has some work done on this but it has not been committed yet. > Hope this answers your question. Well .. i noticed that kvm_getargv indeed only seems to use /proc in case that apparently the commandline argument list grows beyond a certain size, as i have been able to establish by trial and error. I guess my question is .. is kvm_getargv INTENDED to use the /proc aproach in cases the command + argument list grows beyond a certain size. Because if that IS the case .. the manpage doesn't reflect this. -- With kind regards, Pascal Hofstee
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?d8a0b762050106220559f630a6>