Make it easier to generate maps for debugging kallsyms problems.
debug_kallsyms is only a debugging target so no help or silent mode.
Signed-off-by: Keith Owens <[email protected]>
Index: linux/Makefile
===================================================================
--- linux.orig/Makefile 2005-02-25 16:21:44.000000000 +1100
+++ linux/Makefile 2005-02-26 21:30:54.000000000 +1100
@@ -722,6 +722,16 @@ quiet_cmd_kallsyms = KSYM $@
# Needs to visit scripts/ before $(KALLSYMS) can be used.
$(KALLSYMS): scripts ;
+# Generate some data for debugging strange kallsyms problems
+debug_kallsyms: .tmp_map$(last_kallsyms)
+
+.tmp_map%: .tmp_vmlinux% FORCE
+ ($(OBJDUMP) -h $< | awk '/^ +[0-9]/{print $$4 " 0 " $$2}'; $(NM) $<) | sort > $@
+
+.tmp_map3: .tmp_map2
+
+.tmp_map2: .tmp_map1
+
endif # ifdef CONFIG_KALLSYMS
# vmlinux image - including updated kernel symbols
On Sat, Feb 26, 2005 at 09:50:02PM +1100, Keith Owens wrote:
> Make it easier to generate maps for debugging kallsyms problems.
> debug_kallsyms is only a debugging target so no help or silent mode.
>
> Signed-off-by: Keith Owens <[email protected]>
Applied to my kbuild tree.
I will remove it when we stop see kallsyms reports.
Sam
On Mon, 14 Mar 2005 22:43:41 +0100,
Sam Ravnborg <[email protected]> wrote:
>On Sat, Feb 26, 2005 at 09:50:02PM +1100, Keith Owens wrote:
>> Make it easier to generate maps for debugging kallsyms problems.
>> debug_kallsyms is only a debugging target so no help or silent mode.
>>
>> Signed-off-by: Keith Owens <[email protected]>
>Applied to my kbuild tree.
>I will remove it when we stop see kallsyms reports.
Good luck! Most of the kallsyms reports are not really kallsyms bugs,
rather they are caused by the kallsyms checking picking up toolchain
problems.