gdbserver

gdbserver

[kd]

Hi,

I am trying to get gdbserver to run on my mpc823 board. (The precompiled
gdbserver is not working for me, it does not seem to get argc and argv
correctly into main() and always terminates with "usage info".

Using the vanilla gdb-4.18 is of no use, since it has not support for ppc.
Using the gdbserver source that Dan posted here a few weeks back results in
the
the following undefined symbols,
PTRACE_POKEUSR
PTRACE_PEEKUSR
KERNEL_U_ADDR
when compiling low-linux.c
If I define these symbols to 6, 3 and 0 respectively, everything compiles
fine, but the linker fails with the error,
undefined referenve to REGISTER_U_ADDR in function register_addr.

These are defined (for some of the other targets) in directory gdb/config/.
Any idea what is missing?

K.D.


** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

Re: gdbserver

[Jim Lewis]

kd@flaga.is wrote:

> Hi,
>
> I am trying to get gdbserver to run on my mpc823 board. (The precompiled
> gdbserver is not working for me, it does not seem to get argc and argv
> correctly into main() and always terminates with "usage info".
>
> Using the vanilla gdb-4.18 is of no use, since it has not support for ppc.
> Using the gdbserver source that Dan posted here a few weeks back results in
> the
> the following undefined symbols,
> PTRACE_POKEUSR

I ran into build problems as well. Apparently, ptrace.h must have changed. The
macros are now called
PTRACE_POKEUSER
PTRACE_PEEKUSER

In my build, KERNEL_U_ADDR is defined in xm.h, which is a link:
xm.h -> ./../config/powerpc/xm-linux.h
#define KERNEL_U_ADDR 0x0


I built gdbserver in a 4.17 tree from the SRC RPM on the LinuxPPC CD.
xm-linux.h in 4.18 does not have that definition.


>
> PTRACE_PEEKUSR
> KERNEL_U_ADDR
> when compiling low-linux.c
> If I define these symbols to 6, 3 and 0 respectively, everything compiles
> fine, but the linker fails with the error,
> undefined referenve to REGISTER_U_ADDR in function register_addr.
>
> These are defined (for some of the other targets) in directory gdb/config/.
> Any idea what is missing?
>
> K.D.

--
Jim Lewis


** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

Re: gdbserver

[dony]

kd@flaga.is wrote:

> Hi,
>
> I am trying to get gdbserver to run on my mpc823 board. (The precompiled
> gdbserver is not working for me, it does not seem to get argc and argv
> correctly into main() and always terminates with "usage info".
>
> Using the vanilla gdb-4.18 is of no use, since it has not support for ppc.
> Using the gdbserver source that Dan posted here a few weeks back results in
> the
> the following undefined symbols,
> PTRACE_POKEUSR
> PTRACE_PEEKUSR
> KERNEL_U_ADDR
> when compiling low-linux.c

Now I have the same problem. Have you solved it? I downloaded gdbserver.tar.gz
form Dan's web site and put it in the gdb-4.17 's tree
(gdb-4.17/gdb/gdbserver)which are copied from the SRC RPM on the LinuxPPC CD.

If I enter this directory , then type "make", an error occurs:
    make:***No rule to make target '../config/powerpc/linux.mt',needed by
Makefile.Stop
Yes, ../config/powerpc doesn't have file "linux.mt".I don't how to modify
Makefile.

Also I find that there are three symbol link files nm.h , tm.h and xm.h which
are pointed to nm-linux.h , tm-linux.h, and xm-linux.h in ../config/powerpc
respectively. But nm-linux.h and tm.linux.h don't exist , only xm-linux.h
exists in ../config/powerpc.
How do you solve all the above problems?
Thank you very much.
dony


** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

Re: gdbserver

[kd]

Hi,

No I did not solve this. I put it on hold for a while since I can still
able to do development on my i386 system.
But soon I  will have to tackle this again since I will have to start
running the firmware on the final target.
Actually I think I might just insert more memory and run the whole gdb on
the target hardware.....

K.D.



dony wrote:


How do you solve all the above problems?
Thank you very much.
dony


** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

gdbserver

[dony]

Hello,

       Now I want to use gdbserver to debug my test app.
      Running "gdbserver :6666 ./mytest" on the target (Powerpc 860)
show a message:
                    Process ./mytest created :pid=8
      But I don't know how to run gdb on the host (X86). The README
doesn't seem to explain
clearly . It says first running "gdb mytest" on the host and then
"target remote mytarget:6666".
But I don't understand something about "gdb mytest" . At this time
should I run a x86 "gdb" or something like "powerpc-linux-gdb"? And the
"mytest"? Is it compiled with x86 gcc or cross-compiled with
"powerpc-linux-gcc"? Really I am very confused at this point:-((
       Do you have any experience to share with me about how to build
and run gdbserver?
Or do you have any other debug tools which can be used in embedded-linux
environment?
        The README for gdbserver is written by Stu Grossman and Fred
Fish.
        Does someone know their email address?
Thank you very much:-)
dony


** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

Re: gdbserver

[Jesper Skov]

>>>>> "dony" == dony  <dony.he@huawei.com.cn> writes:

dony> Hello,

dony>        Now I want to use gdbserver to debug my test app.
dony> Running "gdbserver :6666 ./mytest" on the target (Powerpc 860)
dony> show a message: Process ./mytest created :pid=8 But I don't know
dony> how to run gdb on the host (X86). The README doesn't seem to
dony> explain clearly . It says first running "gdb mytest" on the host
dony> and then "target remote mytarget:6666".  But I don't understand
dony> something about "gdb mytest" . At this time should I run a x86
dony> "gdb" or something like "powerpc-linux-gdb"? And the "mytest"?


mytest is the same executable you run on the target. gdb you run on
the host would be powerpc-linux-gdb (i.e., cross-debugger), thus:

target:> gdbserver :6666 ./mytest

host:> powerpc-linux-gdb mytest
[...]
(gdb) target remote mytarget:6666




dony> Is it compiled with x86 gcc or cross-compiled with
dony> "powerpc-linux-gcc"? Really I am very confused at this point:-((

mytest is compiled with powerpc-linux-gcc.

dony> Do you have any experience to share with me about how to build
dony> and run gdbserver?  Or do you have any other debug tools which
dony> can be used in embedded-linux environment?  The README for
dony> gdbserver is written by Stu Grossman and Fred Fish.  Does
dony> someone know their email address?  Thank you very much:-) dony

Yes I know their email addresses. But you don't want to hassle them
with this. Trust me :)

Jesper

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

Re: gdbserver

[dony]

Jesper Skov wrote:

> >>>>> "dony" == dony  <dony.he@huawei.com.cn> writes:
>
> dony> Hello,
>
> dony>        Now I want to use gdbserver to debug my test app.
> dony> Running "gdbserver :6666 ./mytest" on the target (Powerpc 860)
> dony> show a message: Process ./mytest created :pid=8 But I don't know
> dony> how to run gdb on the host (X86). The README doesn't seem to
> dony> explain clearly . It says first running "gdb mytest" on the host
> dony> and then "target remote mytarget:6666".  But I don't understand
> dony> something about "gdb mytest" . At this time should I run a x86
> dony> "gdb" or something like "powerpc-linux-gdb"? And the "mytest"?
>
> mytest is the same executable you run on the target. gdb you run on
> the host would be powerpc-linux-gdb (i.e., cross-debugger), thus:
>
> target:> gdbserver :6666 ./mytest
>
> host:> powerpc-linux-gdb mytest
> [...]
> (gdb) target remote mytarget:6666
>
> dony> Is it compiled with x86 gcc or cross-compiled with
> dony> "powerpc-linux-gcc"? Really I am very confused at this point:-((
>
> mytest is compiled with powerpc-linux-gcc.

"powerpc-linux-gdb" is compiled with gcc or powerpc-linux-gcc?


** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

Re: gdbserver

[Jesper Skov]

>>>>> "dony" == dony  <dony.he@huawei.com.cn> writes:

dony> Jesper Skov wrote:

>> >>>>> "dony" == dony <dony.he@huawei.com.cn> writes:
>>
dony> Hello,
>>
dony> Now I want to use gdbserver to debug my test app.  Running
dony> "gdbserver :6666 ./mytest" on the target (Powerpc 860) show a
dony> message: Process ./mytest created :pid=8 But I don't know how to
dony> run gdb on the host (X86). The README doesn't seem to explain
dony> clearly . It says first running "gdb mytest" on the host and
dony> then "target remote mytarget:6666".  But I don't understand
dony> something about "gdb mytest" . At this time should I run a x86
dony> "gdb" or something like "powerpc-linux-gdb"? And the "mytest"?
>>  mytest is the same executable you run on the target. gdb you run
>> on the host would be powerpc-linux-gdb (i.e., cross-debugger),
>> thus:
>>
>> target:> gdbserver :6666 ./mytest
>>
>> host:> powerpc-linux-gdb mytest [...]  (gdb) target remote
>> mytarget:6666
>>
dony> Is it compiled with x86 gcc or cross-compiled with
dony> "powerpc-linux-gcc"? Really I am very confused at this point:-((
>>  mytest is compiled with powerpc-linux-gcc.

dony> "powerpc-linux-gdb" is compiled with gcc or powerpc-linux-gcc?

gcc. You should look at one of the FAQ/HOWTO/READMEs/Home pages on the
sucject of embedded development. I think there was posted a small
howto on compiling the components a few days back. Check the archive.


One question: you are using an x86 host, right? If you use a PPC host,
you can just use the preinstalled GDB/GCC when building/debugging the
target binary.


dony>How do you build you powerpc-linux-gdb?
dony>I copy a gdb-4.17.tar.gz from LinuxPPC R4 CD.
dony>When I untar and decompress it, I type the following  under gdb-4.17/gdb
dony>directory:
dony>
dony>	./configure --target=powerpc-linux
dony>	make
dony>
dony>	It fails to compile and say:
dony> make:*** No rule to make target `../bfd/bfd.h`, needed by `blockframe.o`.Stop.
dony>
dony>Yes, there is not bfd.h under gdb-4.17/bfd directory.
dony>Do you know why?
dony>Thank you very much.


I don't know why. It's an old debugger. I think we keep a more recent
version / CVS tree on sourceware.cygnus.com. It may work better. The
howto I mentioned before included links to the archives used, as far
as I remember.

Jesper

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/