From owner-freebsd-current  Wed Aug  4 14:14: 0 1999
Delivered-To: freebsd-current@freebsd.org
Received: from alcanet.com.au (border.alcanet.com.au [203.62.196.10])
	by hub.freebsd.org (Postfix) with ESMTP id C824414D7D
	for <current@FreeBSD.ORG>; Wed,  4 Aug 1999 14:13:55 -0700 (PDT)
	(envelope-from jeremyp@gsmx07.alcatel.com.au)
Received: by border.alcanet.com.au id <40327>; Thu, 5 Aug 1999 06:54:09 +1000
Date: Thu, 5 Aug 1999 07:13:32 +1000
From: Peter Jeremy <jeremyp@gsmx07.alcatel.com.au>
Subject: Re: Panic plus advice needed
In-reply-to: <199908040936.TAA13368@godzilla.zeta.org.au>
To: archie@whistle.com, bde@zeta.org.au
Cc: current@FreeBSD.ORG
Message-Id: <99Aug5.065409est.40327@border.alcanet.com.au>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Bruce Evans <bde@zeta.org.au> wrote:
>>> >Any objections to the patch below?
>>> 
>>> Yes.  It bloats the kernel and only fixed one cause of the problem.
>>
>>What are the others..?
>
>The only one I can find now is naming the debugging kernel with a name
>of different length.

Also, if your kernel was previously version 9 (or 99 or 999 or ...),
the incremented version number will increase the length of the version
string in vers.c.

Someone with some free time on their hands might like to check thru
the egcs code to see if enabling debug can affect the code generation.
A quick check suggests that the relevant globals are write_symbols,
use_gnu_debug_info_extensions and debug_info_level.  Generating SDB
debugging information (for COFF) definitely can change code alignment,
but working out if generating DBX debugging information has any effect
on the generated code would take more time than I can justify right
now.

Peter


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message