From: Jeff Dike <jdike@addtoit.com>
To: Tom Spink <tspink@gmail.com>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: UML fails to locate address space
Date: Tue, 20 May 2008 09:52:38 -0400 [thread overview]
Message-ID: <20080520135238.GB6990@c2.user-mode-linux.org> (raw)
In-Reply-To: <7b9198260805200408k1d6b70a8xc7e4c24106e5020f@mail.gmail.com>
On Tue, May 20, 2008 at 12:08:24PM +0100, Tom Spink wrote:
> I've just recently pulled the latest GIT and compiled UML, however,
> when I run it a message appears saying "Locating the top of the
> address space... Address 0x0 no good?" and the program exits.
Can you strace it and send me the output?
> After some digging, it appears that page_ok is returning false when
> checking 'bottom', in os_get_task_size
> (arch/um/os-Linux/sys-i386/task_size.c:96). After running through
> GDB, it seems that in line 31 of that file is where the segfault
> occurs:
>
> n = *address;
>
> i.e. when trying to read from the address space (at address zero).
The segfaults are on purpose - it will trap SIGSEGV and longjmp out of
the handler and mark the affected address as not-usable.
Jeff
--
Work email - jdike at linux dot intel dot com
next prev parent reply other threads:[~2008-05-20 13:52 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-20 11:08 UML fails to locate address space Tom Spink
2008-05-20 13:52 ` Jeff Dike [this message]
2008-05-20 13:59 ` Tom Spink
2008-05-20 16:10 ` Jeff Dike
2008-05-20 16:43 ` Tom Spink
2008-05-20 17:56 ` Jeff Dike
2008-05-20 18:01 ` Tom Spink
2008-05-20 19:24 ` Jeff Dike
2008-05-20 19:42 ` Tom Spink
2008-05-20 21:27 ` Jeff Dike
2008-05-20 22:03 ` Tom Spink
2008-05-20 23:57 ` Tom Spink
2008-05-21 1:58 ` Jeff Dike
2008-05-20 15:22 ` linux-os (Dick Johnson)
2008-05-20 17:35 ` Jeff Dike
2008-05-20 21:54 ` linux-os (Dick Johnson)
2008-05-21 2:15 ` Jeff Dike
2008-05-21 12:02 ` Tom Spink
2008-05-21 12:04 ` Tom Spink
2008-05-21 17:58 ` Jeff Dike
2008-05-21 19:01 ` Tom Spink
2008-05-20 21:58 ` linux-os (Dick Johnson)
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20080520135238.GB6990@c2.user-mode-linux.org \
--to=jdike@addtoit.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tspink@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox