Hello? Could somebody please answer the following...
While awaiting answers for the previously-posted message
(see below), I actually got gbd5 and gdbserver5 talking
to each other, however, there were 2 places that I had to
fix and I don't see how it's possible for them to have
talked otherwise.
I manually applied the patch file (by reading the patch
file and manually finding the right place in the patched
file, and then editing it) to what I downloaded from
cvs yesterday.
The two places that were still broken are:
1) the DECR_PC_AFTER_BREAK is still wrong (should
be 4) for arm (at least my version of chip), and
2) the REGISTER_U_ADDR macro definition in the patch
file you sent is incorrect - the definition needs 'addr ='
to be able to return the calculated address.
Furthermore, gdbserver ought to set some speed rather
than just taking whatever speed the driver is set to.
I got V5 Insight to start up now (it couldn't find the init.tcl file
for some reason so I added a soft-link to where it was),
but I still can't debug. When I start it with:
./insight-gdb nop [nop is the name of the test program]
the source displays on the screen. But when I connect to
the target board, the source on the screen vanishes. I have
found no way to get it back, nor to start the program.
Is this the forum for Insight too?
Paul Kinzelman wrote:
> > > Host machine: RH 6.2 i386
> > > Target Machine: Cirrus EDB7211 arm evaluation board running Linux.
> >
> > Ok. Is that an ARM 7500FE based board?
>
> I don't recognize that number. The Cirrus manual says EP7211 chip, is
that
> what you're asking?
>
> > arm-linux-gcc v2.95.2 is preferable.
>
> Hopefully my arm-linux-gcc v2.91.66 will work? I'd rather tackle that
some
> other day.
>
> > > The gdb and insight 5.0 I have is different (in the areas patched
by
> > > your patch file). Please send me a pointer to your 5.0 (gdb and
insight) so
> > > I can start from there with gdb then insight (which will hopefully
match
> > > your patch file). It sounds like redhat may have
> > > their own different V5.0 floating around. That's very confusing.
> >
> > I get my source from the mainline CVS tree at sources.redhat.com for
both gdb
> > and insight. I update frequently. The patches I sent were against
source
> > updated on July 31 I believe.
>
> I just grabbed the CVS tree now and the patch you sent still does not
work.
> It fails immediately (Hunk #1 FAILED at 1014.) I tried it in various
place with
> various -pN numbers just in case. I think if I'm in the gdb50/gdb area
and use
> -p0 it should work, right? I used "patch -p0 < ../gdbserv.patch"
>
> But if I look at the patch file, if I'm interpreting it right, it's
saying that at
> line 1014 in gdb/configure.in, it should
> find "if test "${target}" = ...", but in my copy of gdb/configure.in
(including what
> I just downloaded), line 1014 of gdb/configure.in is blank. The line
it seems to
> want to refer to is 952 in both what I just downloaded from CVS as
well
> as in the tar.gz file I downloaded before. Isn't that why the patch is
failing?
>
> > You shouldn't have to. What kernel and libc are on the Linux
system? Is it ELF
> > or a.out?
>
> The server I'm using to build is 2.2.12-20smp.
> The host debug i386 box is 2.2.14-5.0
> The target arm board is 2.2.1
> I'm using elf for everything.
> How do I find the libc version?
>
> -PaulK
