Hi Jim,<br><br><div class="gmail_quote">On Fri, Dec 9, 2011 at 10:59 PM, Jim Cromie <span dir="ltr"><<a href="mailto:jim.cromie@gmail.com">jim.cromie@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
hi folks,<br>
<br>
out of habit, I build my kernels to a build tree<br>
ie use make O=../build-foo just once,<br>
then cd ../build-foo, and thereafter run make there<br>
<br>
this doesnt play nice with objdump -S<br>
--source<br>
Display source code intermixed with disassembly, if<br>
possible. Implies -d.<br>
<br>
it seems its not possible unless the source and obj are in the same file.<br>
GDB manages to find the source, whats missing in objdump ?<br>
<br>
FWIW, Id love a micro-tutorial on this,<br>
anyone know how to display, dissect the obj file, debuginfo etc ?<br>
or can recommend some on-line tome that gets into it at some breadth and depth ?<br>
many many search hits are for quick Q&A that doesnt get deeper than a puddle.<br></blockquote><div><br>So I normally do out of tree builds, but I always run make from the source tree and specify the O= option.<br><br>
I'm using 3.0.1, and in menuconfig, I went into "Kernel hacking", enabled "Kernel debugging" and then "Compile the kernel with debug info".<br><br>The "Compile the kernel with debug info" option enables CONFIG_DEBUG_INFO which cause the kernel source to be compiled with the -g option which adds the debugging information needed to find the source from the objects.<br>
<br>I normally cross compile for the ARM, so I then cd'd into my build tree and tried arm-linux-gnueabi-objdump -S on a few object files and they all gave intermingled C and assembler listings.<br><br>I tried it using your method and it seemed to work fine for me as well.<br>
<br></div></div>-- <br>Dave Hylands<br>Shuswap, BC, Canada<br><a href="http://www.davehylands.com" target="_blank">http://www.davehylands.com</a><br>