Unfortunately I have zero experience with gdb. It would probably take
longer to learn how to use that than to refresh to the kernel patches on
3.2 to support 3.2.7 so I could try that version to see if its already
fixed.
On 2/28/12 3:08 PM, Philip Prindeville wrote:
% cat /proc/modules
that will give you the base address of each module... you can then gdb what the
load address was of the module on your build host, and as it to print each
address...
On 2/28/12 12:56 PM, Adam Gensler wrote:
I've built a generic x86 image and attempted to get a stack trace by
manually mapping the trace addresses to the System.map file.
Unfortunately, none of the addresses are in the System.map. I suspect,
after having read the following URL, that this is because the call
traces are coming from kernel modules, not the kernel itself (hence the
reference to insmod in the call trace).
http://www.faqs.org/docs/Linux-HOWTO/Kernel-HOWTO.html#systemmap
That URL goes on the explain the System.map and why things like modules
aren't in it. So...now I'm stuck.
On 2/27/12 11:11 PM, Philip Prindeville wrote:
You should be able to get a stack trace with gdb and the unstripped kernel, or
else just do it by hand with:
.tmp_System.map
in your build_dir/linux-x86_alix2/linux-3.2.2/ directory.
Maybe someone else like Felix or Jo-Philipp can give better suggestions?
-Philip
_______________________________________________
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
_______________________________________________
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
