From: Jim Lewis <jlewis@mvista•com>
To: kd@flaga•is
Cc: linuxppc-embedded@lists•linuxppc.org
Subject: Re: gdbserver
Date: Tue, 21 Dec 1999 10:05:14 -0600 [thread overview]
Message-ID: <385FA53A.95617562@mvista.com> (raw)
In-Reply-To: OFFF644F53.7F60D0CE-ON0025684E.0050176B@flaga.is
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/
next prev parent reply other threads:[~1999-12-21 16:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-12-21 14:35 gdbserver kd
1999-12-21 16:05 ` Jim Lewis [this message]
2000-01-21 7:25 ` gdbserver dony
-- strict thread matches above, loose matches on Subject: below --
2000-01-21 12:38 gdbserver kd
2000-01-22 3:20 gdbserver dony
2000-01-22 10:27 ` gdbserver Jesper Skov
2000-01-24 1:51 ` gdbserver dony
2000-01-24 8:20 ` gdbserver Jesper Skov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=385FA53A.95617562@mvista.com \
--to=jlewis@mvista$(echo .)com \
--cc=kd@flaga$(echo .)is \
--cc=linuxppc-embedded@lists$(echo .)linuxppc.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox