Re: arm: Inconsistent kallsyms data

[Keith Owens <kaos@ocs.com.au>]

On Wed, 11 May 2005 12:05:10 +0300, 
Imre Deak <imre.deak@nokia.com> wrote:
>building 2.6.12-rc4 results in "Inconsistent kallsyms data". Setting
>CONFIG_KALLSYMS_EXTRA_PASS=y doesn't help.
>
>I made a diff of .tmp_kallsyms[12].S after converting them to human
>readable form with kallsyms_uncompress.pl .
>
>I noticed that the error is triggered by an __initdata definition. It is
>accessed only from an __init function, so that's ok I think. Removing
>the __initdata attribute gets rid of the error message.
>
>Let me know if you need more data to track the problem.

A better approach is this patch, it extracts the maps including the
section headers after each stage.  I sent it to lkml on Sat, 26 Feb
2005 with no response.  Apply the patch, make debug_kallsyms and send
me the .tmp_map* files.

---

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 <kaos@ocs.com.au>


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


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/