On Thursday, July 6, 2000 at 12:30:00 PM UTC+5:30, S. Johnson wrote:
Alex Ward wrote:
Has anyone here done any remote source level debugging of a vxWorks
target using gdb? Is this sort of debugging possible?
I have seen a reference somewhere that it is/was possible to remotely
debug code on a vxWorks platform over IP. The version of gdb seems to
have been called vxgdb.
There was reference to a library called librdb.a that I gather had to
be linked to the target code. I have not been able to find any mention
of this on the web.
Has any one done this?
TIA
Alex
Sent via Deja.com http://www.deja.com/
Before you buy.
I debug remotely quite often. I sit at my Linux box at home and since
it's running X, I export our Solaris box (the Tornado host) in the office
to my xhost which is connected over a modem.
Then I just launch Tornado I -or- Tornado II. It's no different than
sitting at my desk in the office, except I'm at home which is a big plus. CrossWind (gbd) works without anything special, other than the -g flag
added to CFLAGS so debugging symbols are available.
In this scenario, one could literally be anywhere and connect.
The only thing to worry about is somebody powering off your rack. It's usually good to have a means of resetting the rack remotely. Personally, I just slap a separate BajaPPC (VME) board in the rack with it's own IP connection. If I need to reset the rack, our BSP has a function sysVmeReset() which asserts SYSRESET and resets all boards in the rack.
SJ
Hi Johnson,
Is there any way to remotely debug a vxWorks target without usage of Tornado, just with usage of gdb. Also by vxgdb, Is this provided by Windriver. Do you know of a working version of (vxgdb) on linux.
Regards,
Ranjit
--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)