On 10/7/2014 12:00 PM, joaoandrefe...@sapo.pt wrote: > Citando Frank Rowand <frowand.l...@gmail.com>: > >> On 10/7/2014 4:04 AM, joaoandrefe...@sapo.pt wrote: >> >> < snip > >> >>> >>> 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 >> >> You should not be using sudo. You do not need superuser capabilities >> to use kdmx. If the serial port you are using requires you to be >> superuser to access it then you should instead modify the permissions >> on the serial port or add your user to the group that has permissions >> on the serial port. >> >> Get rid of the pre-built kdmx: >> make clean >> >> (or if that does not work: rm kdmx) >> >> The compile kdmx: >> make >> >> Then print help: >> ./kdmx -h > > Even after reading the help, I'm not 100% sure whether I should run kdmx on > the target (KGDB) or on the host (GDB). It seems to me it is meant to be run > on the target, but if I run it there (after resuming the target kernel boot,
Run kdmx on the host. > of course), I 'll have as output something like: > > /dev/pts/1 is slave pty for for terminal emulator > /dev/pts/2 is slave pty for gdb > > Next, in the host machine, if I try to connect GDB to /dev/pts/2, I'll have: > > (gdb) target remote /dev/pts/2 > Remote debugging using /dev/pts/2 > Ignoring packet error, continuing... > warning: unrecognized item "timeout" in "qSupported" response > Ignoring packet error, continuing... > > What am I doing wrong? > > Again, thanks for everything. > 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
