From: Thomas Schlichter <schlicht@uni-mannheim.de>
To: Sam Ravnborg <sam@ravnborg.org>
Subject: Re: 2.6.0-test3-mm1
Date: Thu, 14 Aug 2003 00:49:19 +0200
User-Agent: KMail/1.5.9
Cc: linux-kernel@vger.kernel.org
References: <20030809203943.3b925a0e.akpm@osdl.org> <3F37DFDC.6080308@mvista.com> <20030813201829.GA15012@mars.ravnborg.org>
In-Reply-To: <20030813201829.GA15012@mars.ravnborg.org>
MIME-Version: 1.0
Content-Disposition: inline
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Message-Id: <200308140049.20465.schlicht@uni-mannheim.de>
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1375
Lines: 31

On Wednesday 13 August 2003 22:18, Sam Ravnborg wrote:
> On Mon, Aug 11, 2003 at 11:26:36AM -0700, George Anzinger wrote:
> > >that patch sets DEBUG_INFO to y by default, even if whether DEBUG_KERNEL
> > >nor KGDB is enabled. The attached patch changes this to enable
> > > DEBUG_INFO by default only if KGDB is enabled.
> >
> > Looks good to me, but.... just what does this turn on?  Its been a
> > long time and me thinks a wee comment here would help me remember next
> > time.
>
> DEBUG_INFO add "-g" to CFLAGS.
> Main reason to introduce this was that many architectures always use
> "-g", so a config option seemed more appropriate.
> I do not agree that this should be dependent on KGDB.
> To my knowledge -g is useful also without using kgdb.

Yes, one can enable or disable DEBUG_INFO as soon as DEBUG_KERNEL is selected, 
this does not depend on KGDB.

With the patch DEBUG_INFO is enabled by default only if KGDB is selected, but 
even if KGDB is not selected you still may enable it by hand.

The problem was that DEBUG_INFO was enabled even if it was not reachable 
because DEBUG_KERNEL was not selected....

  Thomas
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/