The files provided here should go under the directory gdb-4.16/gdb after you
unpack the original gdb-4.16 distribution which is available from various GNU
archives such as gatekeeper.dec.com or ftp.cygnus.com.

Feature list of the stuff you get when you build this gdb:

1. ability to use gdb over a TCP over ethernet connection *reliably*.
2. ability to breakpoint in multiple tasks
3. ability to use both the shell resident assembly level debugger and
remote gdb cooperative fashion
4. ability to use a linear coredump as gdb target (for vxworks target
core mem dump, for postmortem debugging).
5. ability to execute vxworks target shell commands from gdb command
line.
6. ability to debug a specific vxworks task.
7. ability to list and examine vxworks tasks from gdb.


There are other versions of gdb available which works with vxworks.
Unfortunately, over the years I have used vxworks, I have been unable
to find a debugger that works without error, consistently.  Wind river's gdb in
various forms have worked with many bugs and subtle errors.  Most people
tolerate this but I can't.  Therefore I have always used the target shell
resident assembly language level debugger when debugging vxworks programs.
What I did here is to hook the target resident shell debugger with the remote
gdb architecture.

This means that you should have your vxworks target code include
INCLUDE_DEBUG and also INCLUDE_SHELL.   And link in the code from the
file gdb_support.c also located here in this archive.

It's actually quite possible to eliminate dependency on vxworks debug
and shell capability altogether.  GDB can be a good remote shell
interface.  I just haven't gone all that way because I'm lazy.

My gdb-4.16 source tree from which these files have been tar'ed up has
been modified to including the DUEL package (version 1.10) which has a
nice C like extention language for debugging.  This may or may not
cause problems for you.	 If it does (if you have trouble compiling),
then you should let me know.

Basically you should be able to just untar the files from
gdb-vxstuff.tar.gz and compile the stuff and get a newer version of
gdb that will know how to do new stuff.	 This assumes that you have
built gdb before, and your gdb source tree has been properly
configured before for the correct host and target types.  For example,
I have configured my gdb thusly:

        ./configure  --host=sparc-sun-sunos4.1.4 --target=m68k-wrs-vxworks

Which means that I'm using a sparcstation-2 running sunos4.1.4 as my
host development platform.  My target is a generic 68k embedded target
which has an ethernet (mc68360 custom HW) running vxworks.

You should first make sure your original gdb-4.16 distribution builds
correctly.

After that, just untar the gdb-vxstuff.tar.gz (the archive that contains all the
files) file into $(TOP)/gdb-4.16/gdb directory.	 $(TOP) here being any place
you put your gdb source tree into.  Then just compile.

Provided by, Hwa-Jin Bae (bae@mail.com), Piedmont, California
All files are under GNU GPL.