Early drop to debugger with DEBUG_MEMGUARD

[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 of M_NEXTFIT or like, to
> avoid a reuse of the previous allocated range as long as possible.

Ah.

> But, you have some further issue even after the assertion was silenced,
> isn't it ?

Yes; please see
<http://docs.FreeBSD.org/cgi/mid.cgi?20130812160154.GF1570> for a copy
of the message that shows the resulting panic.  (Or see previous
messages i this thread, if that's easier.)  It looks (from my naive
perspective) as if mti_zone hadn't been initialized (properly?  at
all?).

In any case, I remain willing to test, subject to Internet connectivity
flakiness where I am now and other demands on my time.

Peace,
david
-- 
David H. Wolfskill				david at catwhisker.org
Taliban: Evil men with guns afraid of truth from a 14-year old girl.

See http://www.catwhisker.org/~david/publickey.gpg for my public key.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 196 bytes
Desc: not available
URL: <http://lists.freebsd.org/pipermail/freebsd-current/attachments/20130812/36096d20/attachment.sig>