linux-kernel - Re: [PATCH] Pass -g to assembler under CONFIG_DEBUG

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Wed, 11 Jul 2007 14:09:11 -0700
From:	Andrew Morton <akpm@...ux-foundation.org>
To:	Roland McGrath <roland@...hat.com>
Cc:	Linus Torvalds <torvalds@...ux-foundation.org>,
	linux-kernel@...r.kernel.org,
	Jason Wessel <jason.wessel@...driver.com>
Subject: Re: [PATCH] Pass -g to assembler under CONFIG_DEBUG_INFO

On Wed, 11 Jul 2007 11:53:34 -0700 (PDT)
Roland McGrath <roland@...hat.com> wrote:

> 
> The assembler for a while now supports -g to generate source line info just
> like the C compiler does.  Source-level assembly debugging sounds like an
> oxymoron, but it is handy to be able to see the right source file and read
> its comments rather than just the disassembly.  This patch enables -g for
> assembly files when CONFIG_DEBUG_INFO=y and the assembler supports the option.
> 
> Signed-off-by: Roland McGrath <roland@...hat.com>
> ---
>  Makefile |    1 +
>  1 files changed, 1 insertions(+), 0 deletions(-)
> 
> diff --git a/Makefile b/Makefile
> index 8a3c271..88b2252 100644
> --- a/Makefile
> +++ b/Makefile
> @@ -498,6 +498,7 @@ endif
>  
>  ifdef CONFIG_DEBUG_INFO
>  CFLAGS		+= -g
> +AFLAGS		+= $(call as-option, -g)
>  endif
>  
>  # Force gcc to behave correct even for buggy distributions

Jason's kgdb tree does

AFLAGS		+= -gdwarf2

(for all architectures!)  Which is better?
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/