Re: kgdb unuseable with cores on current (for some people)

Benjamin Kaduk wrote:
> On Fri, 14 May 2010, Benjamin Kaduk wrote:
>
>> On Fri, 14 May 2010, Alan Cox wrote:
>>
>>>
>>> I suspect the following is needed:
>>>
>>> Index: vm/vm_page.c
>>> ===================================================================
>>> --- vm/vm_page.c        (revision 207823)
>>> +++ vm/vm_page.c        (working copy)
>>> _at__at_ -108,6 +108,7 _at__at_ __FBSDID("$FreeBSD$");
>>> #include <sys/kernel.h>
>>> #include <sys/limits.h>
>>> #include <sys/malloc.h>
>>> +#include <sys/msgbuf.h>
>>> #include <sys/mutex.h>
>>> #include <sys/proc.h>
>>> #include <sys/sysctl.h>
>>> _at__at_ -375,6 +376,14 _at__at_ vm_page_startup(vm_offset_t vaddr)
>>>            new_end + vm_page_dump_size, VM_PROT_READ | VM_PROT_WRITE);
>>>        bzero((void *)vm_page_dump, vm_page_dump_size);
>>> #endif
>>> +#ifdef __amd64__
>>> +       pa = DMAP_TO_PHYS((vm_offset_t)msgbufp);
>
> If I change this to be msgbufp->msg_ptr, then all works as expected.
>
> While tracking this down, I realized that passing the -q(uiet) 
> argument to kgdb would have been a valid workaround all along.
>
>
> Alan, could you please commit the modified patch?

Yes, it's done.  Thanks,
Alan