Re: Early drop to debugger with DEBUG_MEMGUARD

2013-08-13 Thread David Wolfskill
On Tue, Aug 13, 2013 at 12:44:54PM -1000, Jeff Roberson wrote: > ... > Please try 254308. It is working for me. Starting from: FreeBSD freebeast.catwhisker.org 10.0-CURRENT FreeBSD 10.0-CURRENT #1244 r254279M/254280:143: Tue Aug 13 11:11:06 PDT 2013 r...@freebeast.catwhisker.org:/comm

Re: Early drop to debugger with DEBUG_MEMGUARD

2013-08-13 Thread Jeff Roberson
On Tue, 13 Aug 2013, Jeff Roberson wrote: On Mon, 12 Aug 2013, David Wolfskill wrote: On Tue, Aug 13, 2013 at 08:29:44AM +0300, Konstantin Belousov wrote: ... The r254025 indeed introduced the problem, and Davide pointed out you a workaround for the assertion triggering. Right; I tried one

Re: Early drop to debugger with DEBUG_MEMGUARD

2013-08-13 Thread Jeff Roberson
On Mon, 12 Aug 2013, David Wolfskill wrote: On Tue, Aug 13, 2013 at 08:29:44AM +0300, Konstantin Belousov wrote: ... The r254025 indeed introduced the problem, and Davide pointed out you a workaround for the assertion triggering. Right; I tried one of those -- I hope I got it right... Prope

Re: Early drop to debugger with DEBUG_MEMGUARD

2013-08-12 Thread David Wolfskill
On Tue, Aug 13, 2013 at 08:29:44AM +0300, Konstantin Belousov wrote: > ... > The r254025 indeed introduced the problem, and Davide pointed out you a > workaround for the assertion triggering. Right; I tried one of those -- I hope I got it right... > Proper fix for the memguard requires a policy o

Re: Early drop to debugger with DEBUG_MEMGUARD

2013-08-12 Thread Konstantin Belousov
On Mon, Aug 12, 2013 at 02:44:35PM -0700, David Wolfskill wrote: > On Mon, Aug 12, 2013 at 09:10:55AM -0700, Davide Italiano wrote: > > ... > > OK, I'm not sure I can make an immediate guess on where's the problem > > now (without access to my main workstation), so I think you need to > > wait tomo

Re: Early drop to debugger with DEBUG_MEMGUARD

2013-08-12 Thread David Wolfskill
On Mon, Aug 12, 2013 at 09:10:55AM -0700, Davide Italiano wrote: > ... > OK, I'm not sure I can make an immediate guess on where's the problem > now (without access to my main workstation), so I think you need to > wait tomorrow unless someone beats me to the punch. The best I can say > is that may

Re: Early drop to debugger with DEBUG_MEMGUARD

2013-08-12 Thread Davide Italiano
On Mon, Aug 12, 2013 at 9:01 AM, David Wolfskill wrote: > On Mon, Aug 12, 2013 at 08:30:15AM -0700, Davide Italiano wrote: >> ... >> > Booting... >> > GDB: no debug ports present >> > KDB: debugger backends: ddb >> > KDB: current backend: ddb >> > Copyright (c) 1992-2013 The FreeBSD Project. >> >

Re: Early drop to debugger with DEBUG_MEMGUARD

2013-08-12 Thread David Wolfskill
On Mon, Aug 12, 2013 at 08:30:15AM -0700, Davide Italiano wrote: > ... > > Booting... > > GDB: no debug ports present > > KDB: debugger backends: ddb > > KDB: current backend: ddb > > Copyright (c) 1992-2013 The FreeBSD Project. > > Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993

Re: Early drop to debugger with DEBUG_MEMGUARD

2013-08-12 Thread Davide Italiano
On Mon, Aug 12, 2013 at 8:13 AM, David Wolfskill wrote: > I first noticed this on my laptop on 08 Aug, after having built & booted > > FreeBSD 10.0-CURRENT #975 r253985M/253985:141: Tue Aug 6 05:28:39 PDT > 2013 root@localhost:/common/S4/obj/usr/src/sys/CANARY i386 > > OK. I'm away fr

Early drop to debugger with DEBUG_MEMGUARD

2013-08-12 Thread David Wolfskill
I first noticed this on my laptop on 08 Aug, after having built & booted FreeBSD 10.0-CURRENT #975 r253985M/253985:141: Tue Aug 6 05:28:39 PDT 2013 root@localhost:/common/S4/obj/usr/src/sys/CANARY i386 OK. I'm away from home, and Internet access is a bit flaky, so initially, I suspec