Article View: gnu.gdb.bug
Article #8814Problems using gdb 4.6 in cross development from sun4 to vxWorks
From: Matt Michaelis
Date: Thu, 22 Oct 1992 19:34
Date: Thu, 22 Oct 1992 19:34
48 lines
2812 bytes
2812 bytes
Does anyone know if gdb 4.6 works on a Sun 4 with a vxWorks 68k target? (I am
running vxWorks 5.0.2b.) I have attempted to install this and am having mixed
results at best. The program runs, and connects to my vxWorks target OK, but
attempting to do useful work has been fruitless. For example:
GDB is free software and you are welcome to distribute copies of it
under certain conditions; type "show copying" to see the conditions.
There is absolutely no warranty for GDB; type "show warranty" for details.
GDB 4.6, Copyright 1992 Free Software Foundation, Inc.
(vxgdb) target vxworks elf
Attaching remote machine across net...
Connected to elf.
Looking in Unix path for all loaded modules:
/home/pam3/vw/config/pvsbc2/vxWorks: (no debugging symbols found)...ok
test1.o: ok
Done.
(vxgdb) break test1:71
Breakpoint 1 at 0x150: file test1.c, line 71.
(vxgdb) run test1
Starting program: test1
Program exited normally.
(vxgdb) load test1.o
Reading symbols from test1.o...done.
(vxgdb) break test1.c:71
Breakpoint 1 at 0x150: file test1.c, line 71.
(vxgdb) run test1 1
Starting program: test1 1
Program exited normally.
(vxgdb)
The breakpoint never happens. (It does work on version 3.2 of gdb that
came with vxWorks.) It seems that the debugger can't remember that the file
has been dynamically linked, and instead assumes that the program starts at
0x000000 on the target. I say this because the symbols from vxWorks are
loaded in at the right addresses, and I can do a breakpoint to one of those
addresses properly, (for example "break fdprintf" does work).
Is the fact that I am using the xdr routines that came with vxWorks, and did
not install the ones in the gdb/vx-share directory a possible source of my
problem? Also, which target files do need to be installed? The makefile
lists a few additional files on top of the xdr routines as "TDEPFILES". The
Makefile does not appear to handle a seperate compiler for the target. Am I
missing something, or does the Makefile need some work?
Thanks in advance.
Matt Michaelis
Technical Details
Message-ID:
<1992Oct22.193433.21821@ncar.ucar.edu>Path:
arc1-ca.pugleaf.net!sparky!uunet!stanford.edu!ames!elroy.jpl.nasa.gov!usc!zaphod.mps.ohio-state.edu!cis.ohio-state.edu!stout.atd.ucar.edu!michaeliShow Full Headers
Complete Article Headers
X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: f5053,a07814bc7ada4b9c,start X-Google-Attributes: gidf5053,public X-Google-ArrivalTime: 1992-10-22 18:52:44 PST Newsgroups: gnu.gdb.bug Path: arc1-ca.pugleaf.net!sparky!uunet!stanford.edu!ames!elroy.jpl.nasa.gov!usc!zaphod.mps.ohio-state.edu!cis.ohio-state.edu!stout.atd.ucar.edu!michaeli From: michaeli@stout.atd.ucar.edu (Matt Michaelis) Subject: Problems using gdb 4.6 in cross development from sun4 to vxWorks Message-ID: <1992Oct22.193433.21821@ncar.ucar.edu> Sender: gnulists@ai.mit.edu Organization: Atmospheric Technology Division/NCAR Boulder, CO Distribution: gnu Date: Thu, 22 Oct 1992 19:34:33 GMT Approved: bug-gdb@prep.ai.mit.edu Lines: 50