linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "dong in kang" <dkang@east.isi.edu>
To: <linuxppc-embedded@lists.linuxppc.org>
Subject: gdb configuration for powerpc target on pentium pc
Date: Fri, 6 Jun 2003 14:02:16 -0400	[thread overview]
Message-ID: <000801c32c55$c415ef40$45a97241@Minjoo> (raw)
In-Reply-To: <3439AB3A99ECD5409F3A52ACF814744D158D23@norcom2.norcom.net>


 I'm trying to debug Linux kernel on the Sandpoint X3 with MPC755 CPU board.
I'm using BDI 2000 with GDB.
I configured gdb v.5.3 as follows

  configure --prefix=/usr/local/cross-ppc/host/intel/ --target=powerpc-linux


 While I used the gdb with BDI, the breakpoints set by gdb do not work well.
It doesn't stop.
After a while, I typed Ctrl-C to stop it. Then it shows the messages shown
below.
And then it terminates. Could it be GDB configuration problem?
Has anybody got similar problem?

 Thanks in advance.

 Dong-In

-------------------
Program received signal SIGSTOP, Stopped (signal).
0x0000d048 in todc_mc146818_read_val (addr=255)
    at
/opt/hardhat/previewkit/kernel/linux-2.4.17_mvl21/include/asm/io.h:299
299             __asm__ __volatile__("lbz%U1%X1 %0,%1; eieio" : "=r" (ret) :
"m" (*addr));
(gdb) s
Cannot remove breakpoints because program is no longer writable.
It might be running in another process.
Further execution is probably impossible.
todc_mc146818_read_val (addr=32) at todc_time.c:119
119             return inb(todc_info->nvram_data);
--------------------------------------------------------


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

  reply	other threads:[~2003-06-06 18:02 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-06 17:40 x86(host) --> ppc(tgt) cross-tool-chain Lokesh Kumar
2003-06-06 18:02 ` dong in kang [this message]
2003-06-07  2:13 ` Karim Yaghmour

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='000801c32c55$c415ef40$45a97241@Minjoo' \
    --to=dkang@east.isi.edu \
    --cc=linuxppc-embedded@lists.linuxppc.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).