From owner-freebsd-current@FreeBSD.ORG Wed May 14 09:37:15 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 80A0237B401 for ; Wed, 14 May 2003 09:37:15 -0700 (PDT) Received: from thalia.otenet.gr (thalia.otenet.gr [195.170.0.8]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6B44643F85 for ; Wed, 14 May 2003 09:37:14 -0700 (PDT) (envelope-from keramida@freebsd.org) Received: from gothmog.gr (patr530-a115.otenet.gr [212.205.215.115]) by thalia.otenet.gr (8.12.9/8.12.9) with ESMTP id h4EGbAg4026598; Wed, 14 May 2003 19:37:12 +0300 (EEST) Received: from gothmog.gr (gothmog [127.0.0.1]) by gothmog.gr (8.12.9/8.12.9) with ESMTP id h4EGbAMT021656; Wed, 14 May 2003 19:37:10 +0300 (EEST) (envelope-from keramida@freebsd.org) Received: (from giorgos@localhost) by gothmog.gr (8.12.9/8.12.9/Submit) id h4EGbAda021655; Wed, 14 May 2003 19:37:10 +0300 (EEST) (envelope-from keramida@freebsd.org) Date: Wed, 14 May 2003 19:37:10 +0300 From: Giorgos Keramidas To: Christoph Kukulies Message-ID: <20030514163710.GA13878@gothmog.gr> References: <200305131907.h4DJ7Bf23753@accms33.physik.rwth-aachen.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200305131907.h4DJ7Bf23753@accms33.physik.rwth-aachen.de> cc: freebsd-current@freebsd.org Subject: Re: misfiled PR ? bin/51181 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 14 May 2003 16:37:15 -0000 On 2003-05-13 21:07, Christoph Kukulies wrote: > I was watching a pending gnats PR (51181) I had posted last month > to be marked as 'misfiled' (?) and then landing in bin/51181 though > I think it is a kernel bug. > > bin is refering to programs, right? But a bad malloc kernel > message, coming from netgraph, would that be a kernel bug or not? I've refiled this under kern/. Can you follow up to the PR and add all the relevant error messages you're getting? Does the bad malloc cause a panic? If yes, can you build a debugging kernel and acquire a crash dump and a backtrace of the kernel as described in the Developer's Handbook? Thanks for the notice about the PR category, - Giorgos