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.
> calling GDB on /boot/ directory on the host machine, where I've
> placed the vmlinux file, after following these instructions:
> http://bipinkunal.blogspot.pt/2012/05/kgdb-tutorial.html Apart from a
> possible newbie mistake, I guess I'm doing it right.
>
> Regards, João
< snip >
>> After fixing the code, I've recompiled the kernel and now "trace
>> API error 0x2" error has gone away. However, GDB still can't find
>> kgdb.c. The new output is below.
< snip >
>> Packet received:
>> 36000000ccb59cc00000000038419fc074ff06f780ff06f708f1a1c00000000019174ac09602000060000000680000007b00a1c07b000000ffff0000ffff0000
>>
>>
kgdb_breakpoint (new_kgdb_io_ops=0xc09f4138) at kernel/kgdb.c:1718
>> 1718 kernel/kgdb.c: No such file or directory. in kernel/kgdb.c
>> Sending packet: $qSymbol::#5b...Ack
------------------------------------------------------------------------------
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
