All of lore.kernel.org
 help / color / mirror / Atom feed
From: Momchil Velikov <velco@fadata.bg>
To: Shuangjun Zhu <r44089@email.sps.mot.com>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
	linuxppc-dev@lists.linuxppc.org, linux-kernel@vger.rutgers.edu
Subject: Re: Kernel debug about Linux for PowerPC
Date: Tue, 07 Mar 2000 11:04:26 +0100	[thread overview]
Message-ID: <38C4D42A.1D0C19B3@fadata.bg> (raw)
In-Reply-To: 005601bf87e6$32f88980$69f001dc@sjzhu.sps.mot.com


Shuangjun Zhu wrote:
>
> Hello,
>
> I want to use the gdb to debug the kernel version 2.2.13 for my MPC860
> board.
> So I set the compiler configuration parameter CONFIG_KGDB = YES,
> but when I re-compile the kernel, it complains that
>
> arch/ppc/kernel/kernel.o(.text+0x68ac): undefined reference to
> `getDebugChar'
> arch/ppc/kernel/kernel.o(.text+0x6934): undefined reference to
> `putDebugChar'
>
> PROBLEM:
> what's wrong? I find no define for function "getDebugChar" in arch/ppc
> directory.

You have to write these functions yourself. The stub uses them to
communicate with the debugger through whatever device is available on
the board. See 'Targets' -> 'Remote' -> 'Remote Serial' in GDB docs.

Regards,
-velco

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

  reply	other threads:[~2000-03-07 10:04 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-03-07  3:35 Kernel debug about Linux for PowerPC Shuangjun Zhu
2000-03-07 10:04 ` Momchil Velikov [this message]
2000-03-07 15:24   ` Dan Malek
2000-03-07 16:45     ` Momchil Velikov
  -- strict thread matches above, loose matches on Subject: below --
2000-03-08  3:14 Shuangjun Zhu

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=38C4D42A.1D0C19B3@fadata.bg \
    --to=velco@fadata.bg \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=linux-kernel@vger.rutgers.edu \
    --cc=linuxppc-dev@lists.linuxppc.org \
    --cc=r44089@email.sps.mot.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.