public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Thomas Schlichter <schlicht@uni-mannheim.de>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.0-test3-mm1
Date: Thu, 14 Aug 2003 00:49:19 +0200	[thread overview]
Message-ID: <200308140049.20465.schlicht@uni-mannheim.de> (raw)
In-Reply-To: <20030813201829.GA15012@mars.ravnborg.org>

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

  parent reply	other threads:[~2003-08-13 22:49 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-10  3:39 2.6.0-test3-mm1 Andrew Morton
2003-08-10  9:01 ` 2.6.0-test3-mm1 Gabor MICSKO
2003-08-10  9:08   ` 2.6.0-test3-mm1 Andrew Morton
2003-08-10 17:41 ` 2.6.0-test3-mm1 Thomas Schlichter
2003-08-11 18:26   ` 2.6.0-test3-mm1 George Anzinger
2003-08-13 20:18     ` 2.6.0-test3-mm1 Sam Ravnborg
2003-08-13 20:58       ` 2.6.0-test3-mm1 Martin J. Bligh
2003-08-13 22:49       ` Thomas Schlichter [this message]
2003-08-14  8:17       ` 2.6.0-test3-mm1 and the -g thing George Anzinger
2003-08-11 14:03 ` 2.6.0-test3-mm1 Luiz Capitulino
2003-08-11 14:35 ` 2.6.0-test3-mm1 Martin J. Bligh
2003-08-11 15:17   ` 2.6.0-test3-mm1 Con Kolivas
2003-08-11 18:05   ` 2.6.0-test3-mm1 William Lee Irwin III
2003-08-11 18:57     ` 2.6.0-test3-mm1 Martin J. Bligh
2003-08-11 21:55     ` 2.6.0-test3-mm1 Con Kolivas
2003-08-11 22:19       ` 2.6.0-test3-mm1 William Lee Irwin III
2003-08-11 18:39   ` 2.6.0-test3-mm1 Andrew Morton
2003-08-11 20:17     ` 2.6.0-test3-mm1 Martin J. Bligh
2003-08-11 22:16       ` 2.6.0-test3-mm1 William Lee Irwin III
2003-08-11 22:50         ` 2.6.0-test3-mm1 Martin J. Bligh
2003-08-11 23:00           ` 2.6.0-test3-mm1 Martin J. Bligh
2003-08-11 23:39           ` 2.6.0-test3-mm1 William Lee Irwin III

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200308140049.20465.schlicht@uni-mannheim.de \
    --to=schlicht@uni-mannheim.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sam@ravnborg.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox