Citando joaoandrefe...@sapo.pt:
> Citando Frank Rowand <frowand.l...@gmail.com>:
>
>> 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
>
> Hi again, Frank,
>
> Thanks! I knew I should be missing something. Strangely, none of the
> tutorials I've found online mentioned this important detail. Anyway,
> although as KGDB / GDB seem to be running correctly (at least
> judging from the GBD output), as you pointed out previously, I'm
> looking into using kdmx.
>
> Thanks again,
> João
Hello again,
Just one more doubt, regarding kdmx: after researching a little bit, I
need to confirm that I indeed need to use it, since that in the cases
I've found the setup seemed different from mine (sharing a serial port
among GDB / KGDB). I have two different physical machines (target and
host), each one with its own physical serial port, and a RS-232 cable
making the connection between them (I think this is the "classic"
setup). Sorry for insisting but this doubt arose yesterday.
In the case I really need to use kdmx, following the instructions you
kindly pointed me (http://elinux.org/Kgdb), in the link to Git
provided there
(git://git.kernel.org/pub/scm/utils/kernel/kgdb/agent-proxy.git/) I
can't seem to find the kdmx files. However, accessing the link above
(strikethrough), I'm able to download a kdmx tar.gz. However,
following the instructions in the README-KDMX.txt file, I'm having no
luck:
$ sudo make
make: `kdmx' is up to date.
$ sudo ./kdmx -h
./kdmx: ./kdmx: cannot execute binary file
I must be doing something wrong...
Best regards,
João
------------------------------------------------------------------------------
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
