On Tue, Sep 18, 2007 at 05:00:39PM -0400, Bradshaw, James wrote:
> I'm running into a problem with a 2.6.14.7 UML kernel and I wonder if
> anyone can help. The issue appears to be that memory allocated by a call
> to vmalloc lies outside the UML's virtual memory map, so that a
> subsequent pointer dereference ends up causing a seg fault.
> Continuing past the breakpoint results in a seg fault:
I think this is probably OK. UML uses SIGSEGV for page faults, and
vmalloc memory is faulted in just like process memory.
(gdb) handle SIGSEGV nostop noprint pass
should have the effect that you want.
Jeff
--
Work email - jdike at linux dot intel dot com
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel
