On Mon, 24 Jan 2005 09:37:00 +0200, Peter Pentchev [EMAIL PROTECTED] wrote:
On Sun, Jan 23, 2005 at 01:17:31AM -0800, Pascal Hofstee wrote:
It didn't make it through this time, either. Note that the FreeBSD
mailing list manager rejects attachments of certain types, so if you are
sending a C
On Thu, 6 Jan 2005 22:05:31 -0800, Pascal Hofstee [EMAIL PROTECTED] wrote:
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.
OK .. i created a
OOpps .. forgot to actually attach my kvmtest.
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to [EMAIL PROTECTED]
On Sun, Jan 23, 2005 at 01:17:31AM -0800, Pascal Hofstee wrote:
OOpps .. forgot to actually attach my kvmtest.
It didn't make it through this time, either. Note that the FreeBSD
mailing list manager rejects attachments of certain types, so if you are
sending a C source file as, say,
On Thu, Jan 06, 2005 at 06:21:54PM -0800, Pascal Hofstee wrote:
I guess to sum it all up it all boils down to the following question.
Is it intended that kvm_getargv() apparently has a conditional under
which it depends on the existince of a working /proc .. even though
the manpage states
For the last couple of days i have been looking into why the
gnustep-gui-port actually Needs procfs mounted in order to
successfully build and i managed to track the problem down to being
inside libkvm. I am however no kernel hacker and my gdb-skills have
left me hanging at a point where i simply
On Fri, 7 Jan 2005 05:19:52 +, Christian S.J. Peron [EMAIL PROTECTED]
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
7 matches
Mail list logo
