[Prev][Next][Index][Thread]
Re: serial GDB and UVM / sproc
[I repost this message as the first one was bounced]
It used to work around one year ago but I did not test on the current
OSKit snapshot. Did you enable the following code in sproc/kernel.c
which is currently commented out?
gdb_trap_mask = (1 <<T_PAGE_FAULT) | (1 << T_NO_FPU);
This is necessary to make all page faults be ignored. (By default all
page faults are reported to GDB as SIGSEGV).
Kota
At Fri, 12 Apr 2002 10:24:53 +0000 (/etc/localtime),
Voon-Li Chung <vlchung@cs.uwa.edu.au> wrote:
>
> Hello all,
>
> Could anyone tell me whether the serial GDB support works together with
> the UVM library? When I try to run the example kernel.c I get some
> SIGSEGVs:
>
>
> >> Initializing UVM 120 oskit_uvm_init(); (gdb) UVM: page directory pa =
> 1008000, PTE_BASE = 0x3f800000 UVM: available memory 0x3f160d8 bytes UVM:
> loaded physical memory block [0x1019000 - 0x3c41fff] UVM: 45220 KB (11305
> pages) reserved UVM: kernel VA starts at 0x4000000
>
> Program received signal SIGSEGV, Segmentation fault.
> OSKIT_NETBSD_UVM_pmap_kenter_pa (va=67129344, pa=16879616, prot=3)
> at ../../uvm/netbsd/sys/arch/i386/i386/pmap.c:638 638 opte = *pte;
> (gdb) cont Continuing. kernel assertion "vm" failed: file
> "../../uvm/uvm/x86/oskit_uvm_pfault.c", line 110
>
> Tid:0x1 P:0016f6c0 Backtrace: fp=16be18
> 00115559 00105088 00125961 001116eb _exit(1) called; rebooting...
>
> Program exited with code 01.
>
References: