Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Kevin Paul Herbert <kph@cisco.com>
To: Jun Sun <jsun@mvista.com>
Cc: linux-mips@linux-mips.org
Subject: Re: [PATCH 2.6] DEBUG_INFO, KGDB and etc...
Date: 15 Jan 2004 11:57:35 -0800	[thread overview]
Message-ID: <1074196652.24675.28.camel@shakedown> (raw)
In-Reply-To: <20040115112201.E18368@mvista.com>

In the top level makefile, there is already:

	ifdef CONFIG_DEBUG_INFO
	CFLAGS		+= -g
	endif

I don't see why you need to add it to arch/mips/Makefile. Your Kconfig
changes seem fine though.

Kevin

On Thu, 2004-01-15 at 11:22, Jun Sun wrote:
> This patch adds the missing "-g" gcc option when kgdb is configure.
> Clean up some debugging related options (DEBUG_INFO really should
> go under KGDB and depends its not being selected)
> 
> If no objection, will check it in later.
> 
> And yes, the good news is that kgdb works in 2.6.
> 
> Jun
-- 
Kevin Paul Herbert <kph@cisco.com>
cisco Systems, Inc.

  reply	other threads:[~2004-01-15 19:57 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-15 19:22 [PATCH 2.6] DEBUG_INFO, KGDB and etc Jun Sun
2004-01-15 19:57 ` Kevin Paul Herbert [this message]
2004-01-15 22:09   ` Jun Sun

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=1074196652.24675.28.camel@shakedown \
    --to=kph@cisco.com \
    --cc=jsun@mvista.com \
    --cc=linux-mips@linux-mips.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