From rea-fbsd@codelabs.ru  Sat May 19 09:41:48 2007
Return-Path: <rea-fbsd@codelabs.ru>
Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52])
	by hub.freebsd.org (Postfix) with ESMTP id 5EC8A16A404;
	Sat, 19 May 2007 09:41:48 +0000 (UTC)
	(envelope-from rea-fbsd@codelabs.ru)
Received: from pobox.codelabs.ru (pobox.codelabs.ru [144.206.177.45])
	by mx1.freebsd.org (Postfix) with ESMTP id 185BC13C4AD;
	Sat, 19 May 2007 09:41:47 +0000 (UTC)
	(envelope-from rea-fbsd@codelabs.ru)
Received: from void.codelabs.ru (void.codelabs.ru [144.206.177.25])
	by pobox.codelabs.ru with esmtpsa (TLSv1:AES256-SHA:256)
	id 1HpLRb-0005L2-2Z; Sat, 19 May 2007 13:41:47 +0400
Message-Id: <20070519094142.GC14426@void.codelabs.ru>
Date: Sat, 19 May 2007 13:41:42 +0400
From: Eygene Ryabinkin <rea-fbsd@codelabs.ru>
Sender: rea-fbsd@codelabs.ru
To: Jason Evans <jasone@freebsd.org>
Cc: FreeBSD-gnats-submit@freebsd.org
In-Reply-To: <464EBDD5.1000601@freebsd.org>
Subject: Re: unwrapped magic checks in the malloc code
References: <20070518220855.81FCBB85C@void.codelabs.ru> <464EBDD5.1000601@freebsd.org>

>Number:         112782
>Category:       kern
>Synopsis:       Re: unwrapped magic checks in the malloc code
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    freebsd-bugs
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Sat May 19 09:50:05 GMT 2007
>Closed-Date:    Sun May 20 07:34:37 GMT 2007
>Last-Modified:  Sun May 20 07:34:37 GMT 2007
>Originator:     
>Release:        
>Organization:
>Environment:
>Description:
 Jason, good day.
 
 Sat, May 19, 2007 at 02:05:25AM -0700, Jason Evans wrote:
 > I don't think it is possible for this to cause a compilation error, due to the
 > logic that assures NDEBUG and MALLOC_DEBUG are set in a mutually coherent 
 > manner.
 
 Yes, you're right: I had overlooked that the NDEBUG is mangled
 basing on the value of the MALLOC_DEBUG.  In principle, one can
 later do something nasty with the NDEBUG that will broke the coherency
 and this will result in the non-compilable code.  Though it will
 be rather easy to find out.
 
 > Is there some set of compilation flags that can cause compilation to 
 > fail?
 
 No, I was just digging through the code and (wrongly) assumed that
 an inconsistency had been found.
 
 Sorry for the noise.  The PR can be closed.
 -- 
 Eygene
>How-To-Repeat:
>Fix:
>Release-Note:
>Audit-Trail:
State-Changed-From-To: open->closed 
State-Changed-By: linimon 
State-Changed-When: Sun May 20 07:34:03 UTC 2007 
State-Changed-Why:  
Misfiled followup to kern/112771; content migrated. 


Responsible-Changed-From-To: gnats-admin->freebsd-bugs 
Responsible-Changed-By: linimon 
Responsible-Changed-When: Sun May 20 07:34:03 UTC 2007 
Responsible-Changed-Why:  

http://www.freebsd.org/cgi/query-pr.cgi?pr=112782 
>Unformatted:
