Questions on GDB

Alagu Sankar alagu@realnetsi.com
Fri Jun 2 14:20:00 GMT 2000


Hello,

I am using gdb 4.18 with wiggler for mpc8xx on a win nt hosted system. I
am using cygwin tools and cross compiler for powerpc-eabi target.

I am able to connect to the target but unable to modify the registers.
When i try to set the processor for 860 my info registers command fails as
following

"read_bdm_registers : sr0    Invalid CPU register access attempt failed"

I see people taking about 'ocd reg' command for modifying the special
purpose. But this is not availabe in gdb 4.18.  Is there a patch for it
somewhere?

Regards,

Alagu



Will Lentz wrote:

> Hi Pete,
>
> For a remote PPC target (through rproxy), I use:
>  file xyz.elf
>  target remote ip.addr:port
>  load
>  run
>
> It's really cool that you ported the Macraigor DLL to Linux!  I
> think more people would use the Wiggler if your port was made
> available :-).
>
> Will
>
> > -----Original Message-----
> > From: Peter Reilley [ mailto:micrio@mv.com ]
> > Sent: Thursday, June 01, 2000 2:24 PM
> > To: gdb@sourceware.cygnus.com
> > Subject: Questions on GDB
> >
> >
> > I have a few questions on the operation of GDB with the Wiggler
> > and a PowerPC target.
> >
> > I have ported the Macraigor DLL from MS Windows to Linux and
> > am attempting to get GDB working.   I can read and write registers
> > and memory in the PPC target.   I have a small test program that
> > I compiled with GCC configured as a cross compiler for the PPC.
> > I can use the "load" command and have the binary load properly
> > in the target memory.   I can use the "symbol-file" command to
> > load the symbols.   The "file" command will load the binary but
> > it seems to have a base address in the host and not the target.
> > The "run" and "step" commands do not seem to work.
> >
> > Anyway, what are the commands that you used to load and execute
> > a binary in a target under Windows.   The documentation that I found
> > on the internet is conflicting.
> >
> > Thanks,
> > Pete.
> >
> >
> >
> >
> >


More information about the Gdb mailing list