On 10/3/2014 11:14 AM, joaoandrefe...@sapo.pt wrote: > Citando Frank Rowand <frowand.l...@gmail.com>: > >> On 10/3/2014 4:03 AM, joaoandrefe...@sapo.pt wrote: >>> Hello again, >>> >>> By the way, while googling for this error I've noticed that a >>> common mistake is to invoke GDB on the wrong location (e. g. >>> http://ehc.ac/p/kgdb/mailman/message/23341685/). What I'm doing >>> is >> >> ^^^^ The answer is in that link. As I mentioned before, invoke >> gdb from the root of your kernel source tree. Since your vmlinux >> is in a different directory, you can supply the absolute path of >> vmlinux in the gdb command line. > > Sorry, but I think I'm not fully understanding this. I don't know > exactly what do you mean by "kernel source tree" in the host machine. > In the target (KGDB), I guess it's /usr/src/linux, since it was there > I've compiled the kernel. In the host (GDB), apart from the vmlinux > file, I don't know what else relates to the kernel I'm trying to > debug on the target. I've tried to launch "gdb /boot/vmlinux" in both > / and /usr/src, but things are't changing. So, a newbie doubt has > arrived, can you enlighten me? Thanks for your patience!
No problem (on the patience). You guessed correctly, you need the kernel source tree that you used to compile the kernel for the target. Since you compiled on the target, you will have to copy that source tree to your host system (the one you run gdb on). -Frnk ------------------------------------------------------------------------------ Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk _______________________________________________ Kgdb-bugreport mailing list Kgdb-bugreport@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/kgdb-bugreport
