Date: Fri, 26 Feb 2010 15:00:37 +0100 From: =?ISO-8859-1?Q?Fernando_Apestegu=EDa?= <fernando.apesteguia@gmail.com> To: Kostik Belousov <kostikbel@gmail.com> Cc: freebsd-emulation@freebsd.org Subject: Re: linprocfs proc/pid/mem Bad address Message-ID: <1bd550a01002260600x4d83d610k3149374143ade77c@mail.gmail.com> In-Reply-To: <20100226111216.GE2489@deviant.kiev.zoral.com.ua> References: <1bd550a01002251354v7ea3ede9r458c027b038280fc@mail.gmail.com> <20100226104147.GC2489@deviant.kiev.zoral.com.ua> <1bd550a01002260306t10e1d287wc634e47848020ddc@mail.gmail.com> <20100226111216.GE2489@deviant.kiev.zoral.com.ua>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, Feb 26, 2010 at 12:12 PM, Kostik Belousov <kostikbel@gmail.com> wrote: > On Fri, Feb 26, 2010 at 12:06:07PM +0100, Fernando Apestegu?a wrote: >> On Fri, Feb 26, 2010 at 11:41 AM, Kostik Belousov <kostikbel@gmail.com> wrote: >> > On Thu, Feb 25, 2010 at 10:54:02PM +0100, Fernando Apestegu?a wrote: >> >> Why /compat/linux/proc/<pid>/mem always reports "Bad address" ? >> >> >> >> I'm using 8.0-RELEASE-p2 >> >> >> >> Thanks in advance. >> > >> > Reports when ? What is the operation you doing that causes this ? >> >> Oops, sorry. When trying to cat the file for example. In Linux the >> error reported is something like >> "No such process" >> >> > > > mem provides access to the target process virtual address space as file. > Reading from the file at some offset returns corresponding sequence of > bytes present in the process virtual address space starting at the offset. > Since cat starts read at the file offset 0, and (almost) no processes > map the page at the address 0, you get this error. Thanks for the clarification. >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1bd550a01002260600x4d83d610k3149374143ade77c>