Lets assume that you have booted a good system and have verified that
the serial link works and that you have configured the host to the
indicated baud rate using setserial or stty. You should put a file
called .gdbinit in the top level kernel source directory (where vmlinux
shows up after a build):
set remotebreak 1
target remote /dev/ttyS3
(Note, change ttyS3 to your serial port name)
Now in that same "working directory" run "gdb vmlinux" or "xgdb vmlinux"
or from emacs: M-x gdb followed by "gdb vmlinux". This last is the way
I like to do it.
That should do it.
Vinodkumar Parasmal wrote:
> Hi all ,
> We have 2 Linux Machines (redhat 6.1 2.2.12-20) one development and
> target m/c, connected back to back by a cross cable.
> we applied the patch from from kgdb and went step by step as explained.
> The "Readme" says that "after applying the patch, when u boot the
> target machine and pass "gdb" to the kernel, it should wait for gdb
> connection via
> the serial connection from the remote machine"(development m/c )
> .Accordingly it waits for connection .
> Now what should be done on the development machine to enable the
> gdb to connect to the remote machine
> my lilo.conf for target machine looks like this
> append="gdb gdbttyS gdbbaud=38400
> thanks in advance
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to email@example.com
> Please read the FAQ at http://www.tux.org/lkml/
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to firstname.lastname@example.org
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Sun Apr 30 2000 - 21:00:14 EST