The problem is that I can use the same way to debug 32bit env. Also, I can see the debugging symbol and line numbers from the ko file.
Thanks, Neo On Sun, Jul 20, 2008 at 4:37 PM, Michael Snyder <[EMAIL PROTECTED]> wrote: > I have a vague recollection to the effect that kernel modules > can be debugged in somewhat the same manner as shared libraries, > but a quick google search didn't turn up anything very useful. > > Never done it myself, don't know anything more specific than that. > > On Fri, 2008-07-18 at 01:02 -0700, Neo Jia wrote: >> Sorry, re-send with plain-text. >> >> Thanks, >> Neo >> >> On Fri, Jul 18, 2008 at 1:00 AM, Neo Jia <[EMAIL PROTECTED]> wrote: >> > >> > hi, >> > >> > I am using the gdb to debug Linux kernel module on x86-64 bit with a >> > patched kernel (kgdb). Everything works fine for the kernel itself, I can >> > break on any functions, and see the sources. But, I can't break on the >> > symbols in the kernel module after it is loaded. I used the >> > "add-symbol-files" to add the sections for that loadable module. >> > >> > The same setup works fine for 32bit and I even can see the symbols/sources >> > by running gdb directly against the 64bit .ko file. >> > >> > Any suggestions? I am struggling with this question for a long time. >> > >> > Thanks, >> > Neo >> > >> > -- >> > I would remember that if researchers were not ambitious >> > probably today we haven't the technology we are using! >> >> >> >> -- >> I would remember that if researchers were not ambitious >> probably today we haven't the technology we are using! > > -- I would remember that if researchers were not ambitious probably today we haven't the technology we are using!
