From: Sam Ravnborg <sam@ravnborg.org>
To: Mithlesh Thukral <mithlesh@linsyssoft.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Problem of debugging modules on x86_64 platform using KGDB
Date: Wed, 8 Sep 2004 11:18:19 +0200 [thread overview]
Message-ID: <20040908091819.GA8918@mars.ravnborg.org> (raw)
In-Reply-To: <1094626891.1101.55.camel@krypton>
On Wed, Sep 08, 2004 at 12:31:31PM +0530, Mithlesh Thukral wrote:
> hi,
> On the x86_64 platform we faced a problem of debugging modules using
> KGDB.
> For working around the problem, we need the compile the file
> 'arch/x86_64/kernel/vsyscall.c' without the generation of debugging
> information.
> For this i moved the 'vsyscall.c' from the directory
> 'arch/x86_64/kernel' to a new directory 'arch/x86_64/kernel/vsyscall/' .
> The make file in this new directory does not generate the debugging
> information for the file 'vsyscall.c'.
> Please let me know if there is some other way by which i can specify a
> different set of compilation flags for a single file in the directory.
> this will help me in not moving the file in a new directory.
In arch/x86_64/kernel/Makfile:
CFLAGS_vsyscalls.o := -g0
That should do the trick.
Use make V=1 to check which flags are passed to gcc.
See also Documentation/kbuild/makefiles.txt for reference.
Sam
prev parent reply other threads:[~2004-09-08 7:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-08 7:01 Problem of debugging modules on x86_64 platform using KGDB Mithlesh Thukral
2004-09-08 9:18 ` Sam Ravnborg [this message]
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=20040908091819.GA8918@mars.ravnborg.org \
--to=sam@ravnborg.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mithlesh@linsyssoft.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.